-
Notifications
You must be signed in to change notification settings - Fork 158
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
Comments
Sounds like a good plan! |
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 |
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? |
Thanks @scottslowe and @SharpEdgeMarshall for our feedback! It appears that I incorrectly interpreted the |
Cannot close issue:
Please fix these problems and try again. |
Hello!
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:
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
The text was updated successfully, but these errors were encountered: