-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
Kubernetes investigate: running the control plane 1-2 versions ahead of the worker nodes - skew policy #84
Comments
EKS testing 1.30 to 1.31 upgrade
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some kubernetes providers push towards the latest (currently 1.32) version. Staying on an older version can cause extended support finops issues.
https://aws.amazon.com/blogs/containers/amazon-eks-extended-support-for-kubernetes-versions-pricing/
see AWS cluster insights
https://docs.aws.amazon.com/eks/latest/userguide/cluster-insights.html
we are used to kubectl skew, test out skew on the cluster with ideally workloads using services near or at deprecation
https://kubernetes.io/releases/version-skew-policy/
The text was updated successfully, but these errors were encountered: