Open t0yv0 opened 10 months ago
Add default_addons_to_remove to schema
Reading this further, this patch seems to implement the following property not supported by the upstream provider:
default_addons_to_remove Sequence[str] List of addons to remove upon creation. Any addon listed will be "adopted" and then removed. This allows for the creation of a baremetal cluster where no addon is deployed and direct management of addons via Pulumi Kubernetes resources. Valid entries are kube-proxy, coredns and vpc-cni. Only works on first creation of a cluster.
The patch adds a TF test for the feature but it is not currently exercised in CI or tested at Pulumi provider level.
Reportedly AWS added the functionality to create EKS clusters without any addons.
Tracking context on upstream patch 0008-Add-EKS-cluster-default_addons_to_remove.patch here.