Open lajchon opened 3 days ago
we depend on the TF Provider: https://github.com/hashicorp/terraform-provider-aws/issues/38156 and this open PR here: https://github.com/hashicorp/terraform-provider-aws/pull/38162
Great that Amazon addresses this! This would be a high priority issue for us since we currently have to work with all kinds of workarounds in order to get rid of the Amazon VPC CNI and reinstall a new CNI afterwards.
What problem are you facing?
Currently, EKS Cluster creation defaults to installing several components: CoreDNS, kube-proxy, and VPC CNI. Announced by Amazon yesterday, here, a new CLI flag is available,
bootstrapSelfManagedAddons
, to disable the automatic deployment of these components.Creating an Amazon EKS cluster
By default, EKS installs multiple networking add-ons during cluster creation. This includes the Amazon VPC CNI, CoreDNS, and kube-proxy.
If you'd like to disable the installation of these default networking add-ons, use the parameter below. This may be used for alternate CNIs, such as Cilium. Review the EKS API reference for more information.
aws eks create-cluster --bootstrapSelfManagedAddons false