Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate eks.Cluster defaultAddonsToRemoves property #3009

Closed
t0yv0 opened this issue Nov 15, 2023 · 5 comments
Closed

Deprecate eks.Cluster defaultAddonsToRemoves property #3009

t0yv0 opened this issue Nov 15, 2023 · 5 comments
Assignees
Labels
kind/enhancement Improvements or new features resolution/wont-fix This issue won't be fixed

Comments

@t0yv0
Copy link
Member

t0yv0 commented Nov 15, 2023

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

In a recent investigation of the patch conflict (#2732 and #2998) it came up that we use upstream patching to implement default_addon_to_remove property (which pluralizes in Pulumi as defaultAddonToRemoves). This property seems to implement create hooks to remove eks.Cluster addons.

When trying to write a test for this functionality it appears that it is now redundant:

  • provision simple eks.Cluster
  • run aws eks list-addons --cluster-name cluster-b83e45e
  • # { "addons": [] "

The cluster does not provision any addons by default. Instead, eks.Addon is a resource that users can opt into to provision the addons that are needed.

Suggest making this property a no-op, removing upstream patches, pertaining to it, and making it as deprecated to remove in a future version.

Affected area/feature

@t0yv0 t0yv0 added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Nov 15, 2023
@mikhailshilkov mikhailshilkov added area/patch An issue describing an existing patch on upstream and the criteria to close it. and removed needs-triage Needs attention from the triage team labels Nov 17, 2023
@mikhailshilkov
Copy link
Member

Sounds like a good plan!

@SharpEdgeMarshall
Copy link

Sorry @t0yv0, I just checked and the creation of a new EKS cluster provision the 3 default addons (vpc-cni, core-dns, kubeproxy) even if the command aws eks list-addons --cluster-name <my-cluster> returns an empty list.
If the feature will be removed, how we are supposed to remove default addons?

@t0yv0 t0yv0 removed the area/patch An issue describing an existing patch on upstream and the criteria to close it. label Mar 25, 2024
@scottslowe
Copy link

My experience mirrors that of @SharpEdgeMarshall; even when I don't explicitly specify add-ons in my Pulumi code I'll still get VPC CNI, kube-proxy, and CoreDNS. If these add-ons are going to be installed by default, then how will users opt-out without this property?

@t0yv0
Copy link
Member Author

t0yv0 commented Apr 19, 2024

Thanks @scottslowe and @SharpEdgeMarshall for our feedback! It appears that I incorrectly interpreted the aws eks list-addons --cluster-name cluster-b83e45e results as authoritative. If this is being relied on we will keep the option. Thank you!

@t0yv0 t0yv0 closed this as completed Apr 19, 2024
@pulumi-bot pulumi-bot reopened this Apr 19, 2024
@pulumi-bot
Copy link
Contributor

Cannot close issue:

  • does not have required labels: resolution/

Please fix these problems and try again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features resolution/wont-fix This issue won't be fixed
Projects
None yet
Development

No branches or pull requests

5 participants