We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After upgrading EKS to 1.21 upgrade core deployments and daemon sets that are recommended for EKS 1.21.
CoreDNS https://docs.aws.amazon.com/eks/latest/userguide/managing-coredns.html
Kube-proxy https://docs.aws.amazon.com/eks/latest/userguide/managing-kube-proxy.html
VPC CNI https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html
The text was updated successfully, but these errors were encountered:
Blocked until these get resolved:
aws/amazon-vpc-cni-k8s#1930 aws/amazon-vpc-cni-k8s#1425
Sorry, something went wrong.
Raised a separate ticket for CNI addon #3640
Applied on both manager and live cluster ministryofjustice/cloud-platform-infrastructure#1507
vijay-veeranki
No branches or pull requests
After upgrading EKS to 1.21
upgrade core deployments and daemon sets that are recommended for EKS 1.21.
CoreDNS
https://docs.aws.amazon.com/eks/latest/userguide/managing-coredns.html
Kube-proxy
https://docs.aws.amazon.com/eks/latest/userguide/managing-kube-proxy.html
VPC CNI
https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html
Definition of done
The text was updated successfully, but these errors were encountered: