Deprecate EKS cluster property defaultAddonsToRemoves in favor of bootstrapSelfManagedAddons

[flostadler]

The defaultAddonsToRemove property was introduced to EKS cluster configuration to allow bootstrapping clusters without AWS's default components (coredns, vpc-cni, kube-proxy). This was implemented in a patch, through a workaround where the provider would:

1. Create an EKS addon on cluster creation
2. Delete it immediately after
3. This effectively brought the cluster components under Pulumi's management before destroying them

Current Situation

AWS has now introduced native support for this functionality through the bootstrapSelfManagedAddons flag, which creates a blank cluster without default components.

Key differences:

• defaultAddonsToRemove: Allows selective removal of specific addons
• bootstrapSelfManagedAddons: All-or-nothing approach (creates a blank cluster). Is faster as it doesn't have to first install the components, adopt them and finally destroy them

Proposed Changes

1. Mark defaultAddonsToRemove as deprecated
2. Remove the property in the next major version

Required Investigation

Before proceeding with deprecation:

1. Analyze current usage patterns of defaultAddonsToRemove
   • Identify how users are utilizing the selective removal capability
   • Determine if there are common patterns that would be broken by moving to an all-or-nothing approach
2. Evaluate potential migration paths for users who need selective addon removal
3. Consider if we need to maintain both options or if AWS's solution sufficiently covers all use cases

References

• Original implementation: Patch #0028
• AWS Announcement

[t0yv0]

There was some pushback on #3009 before but I think what was missing is allowing users to still not get the addons wihch is now made available with bootstrapSelfManagedAddons. Thanks for filing!