So you did something silly on your EKS cluster?

$ kubectl delete all --all -A
pod "aws-node-4ph22" deleted
pod "aws-node-4s6ws" deleted
pod "aws-node-v2hpf" deleted
pod "coredns-996495cbb-ktgtl" deleted
pod "coredns-996495cbb-wdn6r" deleted
pod "kube-proxy-78q8w" deleted
pod "kube-proxy-f47xz" deleted
pod "kube-proxy-sbpbh" deleted
service "kubernetes" deleted
service "kube-dns" deleted
daemonset.apps "aws-node" deleted
daemonset.apps "kube-proxy" deleted
deployment.apps "coredns" deleted

Ensure your version of the AWS CLI is at least version 1.20 or higher to provide the EKS addon functionality documented in the following links:

• https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html
• https://docs.aws.amazon.com/eks/latest/userguide/managing-coredns.html
• https://docs.aws.amazon.com/eks/latest/userguide/managing-kube-proxy.html

$ aws eks create-addon --cluster-name NAME --addon-name vpc-cni --resolve-conflicts OVERWRITE
$ aws eks create-addon --cluster-name NAME --addon-name coredns --resolve-conflicts OVERWRITE
$ aws eks create-addon --cluster-name NAME --addon-name kube-proxy --resolve-conflicts OVERWRITE