pulumi-aws
pulumi-aws copied to clipboard
PATCH 0029-aws_eks_cluster-implement-default_addons_to_remove.patch
Tracking context on upstream patch 0008-Add-EKS-cluster-default_addons_to_remove.patch here.
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.