- Newest
- Most votes
- Most comments
Easiest way is to just install the equivalent EKS addons using the overwrite flag - which take over ownership of the unmanaged addons. Then delete the EKS addons.
To properly uninstall unmanaged EKS add-ons like VPC CNI, CoreDNS, and kube-proxy, follow these steps:
-
For VPC CNI:
- Use kubectl to delete all associated resources including the DaemonSet, ConfigMap, ClusterRole, and ClusterRoleBinding.
- Refer to the aws/amazon-vpc-cni-k8s GitHub repository for the complete list of resources to remove.
- Be cautious when removing VPC CNI if you have Fargate nodes, as they require this plugin.
-
For kube-proxy:
- Delete the kube-proxy DaemonSet, ConfigMap, and related RBAC resources using kubectl.
- Ensure you have an alternative networking solution ready.
-
For CoreDNS:
- Remove the CoreDNS Deployment, ConfigMap, and associated RBAC resources with kubectl.
- Have an alternative DNS solution prepared.
Important considerations:
- Back up your cluster configuration before making changes.
- Test the uninstallation process in a non-production environment first.
- Ensure alternative solutions are in place for networking and DNS.
- Be aware that removing these components may impact cluster functionality, especially for Fargate nodes.
Remember, while it's possible to remove these components, doing so can affect cluster stability and functionality. Always thoroughly test and understand the implications before applying changes to production clusters.
Sources
Amazon EKS examples using AWS CLI - AWS SDK Code Examples
Remove an Amazon EKS add-on from a cluster - Amazon EKS
DeleteAddon - Amazon EKS
GenAI generated closely to my input. I can't tell if this is hallucination or not. I don't trust this without expert human review
Relevant content
- asked 3 years ago
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago

Thanks for sharing! How I managed to remove addons: