Skip to content

Consistent EKS addon management for vpc-cni and kube-proxy #5550

@MinhNguyen-at

Description

@MinhNguyen-at

/kind feature
Thanks to #5520 CAPA is on its way to provide some resemblance of the ability to migrate to self-managed versions of eks addons.

Currently, vpc-cni and kube-proxy are explicitly reconciled separately regardless of what is listed as an addon. vpc-cni reconciliation has the label "aws.cluster.x-k8s.io/prevent-deletion" to allow short-circuiting the ReconcileCNI() while ReconcileKubeProxy() does not.

It would be nice to have a consistent story for addons and migrating to self-managed versions of addons.

Proposed solution(s):
a) add annotation/label check for deletion prevention to short circuit ReconcileKubeProxy, similar to ReconcileCNI.
b) remove ReconcileKubeProxy and ReconcileCNI and have them as managed addons.

B is cleaner schema wise but would make it more difficult for existing users to upgrade CAPA versions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.needs-priorityneeds-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions