Add bootstrapSelfManagedAddons to Cluster EKS Provider spec

[lajchon]

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

[haarchri]

we depend on the TF Provider: hashicorp/terraform-provider-aws#38156 and this open PR here: hashicorp/terraform-provider-aws#38162

[mithie]

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.

[mergenci]

Looks like bootstrapSelfManagedAddons attribute was introduced with the Terraform provider v5.58.0 version bump.