You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Go through the EKS and Kubernetes release notes for version and create a plan to upgrade our clusters
Things to consider:
Review EKS / Kubernetes changelogs & release notes
EKS Module supported at target upgrade version?
Are there any API deprecations & removals? (Check EKS insights)
Are there new components being added?
What changes are being introduced to current components?
Are there changes to core infra of the CP required? i.e. Are all our current components compatible with ?
Are there changes users need to make?
Do we need to expand any of our smoke/integration testing?
Create additional tickets needed for any findings specific to this upgrade
Review the compatibility matrix of kube-state-metrics and verify if the image is compatible with the upgraded Kubernetes version. If the version is a mismatch, check if the whole kube-prometheus-chart needs updating to get the default version of kube-state-metrics from the chart-> values. Otherwise, pin the kube-state-metrics image to match the Kubernetes version.
Issue 13:
Upgrade cluster autoscaler for EKS version
The Cloud Platform EKS Cluster is in Kubernetes version . Hence upgrade the cluster-autoscaler to match the Kubernetes version.
Following upgrade to EKS , there will be a number of cleanup activities that need addressing:
Update user guide / runbook references to EKS version
Update tools-image for kubectl version
Update cloud-platform-cli for kubectl version
Update concourse pipelines to use updated tools-image and cli
Issue 16:
Update Upgrade runbook and Cluster Upgrade Issue Template
Update the runbook for
any changes needed in the steps to perform the upgrade
any lessons learnt that could be useful for next upgrade
Issue 1:
Planning upgrade to EKS
Go through the EKS and Kubernetes release notes for version and create a plan to upgrade our clusters
Things to consider:
Review EKS / Kubernetes changelogs & release notes
EKS Module supported at target upgrade version?
Are there any API deprecations & removals? (Check EKS insights)
Are there new components being added?
What changes are being introduced to current components?
Are there changes to core infra of the CP required? i.e. Are all our current components compatible with ?
Are there changes users need to make?
Do we need to expand any of our smoke/integration testing?
Create additional tickets needed for any findings specific to this upgrade
Cluster upgrade Runbook:
https://runbooks.cloud-platform.service.justice.gov.uk/upgrade-eks-cluster.html
Issue 2:
Update vpc-cni to latest supported release for current EKS version
Check for the latest supported addon release for the current EKS version and update the clusters
Runbook link
Production Clusters Checklist:
See the Amazon EKS add-ons documentation for more information about addons, or find the latest versions for these EKS add-ons directly:
Issue 3:
Update kube-proxy to latest supported release for current EKS version
Check for the latest supported addon release for the current EKS version and update the clusters
Runbook link
Production Clusters Checklist:
See the Amazon EKS add-ons documentation for more information about addons, or find the latest versions for these EKS add-ons directly:
Issue 4:
Update core-dns to latest supported release for current EKS version
Check for the latest supported addon release for the current EKS version and update the clusters
Runbook link
Production Clusters Checklist:
See the Amazon EKS add-ons documentation for more information about addons, or find the latest versions for these EKS add-ons directly:
Issue 5:
Test EKS on test cluster
Follow instructions from Upgrade runbook: https://runbooks.cloud-platform.service.justice.gov.uk/upgrade-eks-cluster.html#upgrade-eks-cluster
Issue 6:
Test EKS on live-like cluster
Follow instructions from creating a live like cluster runbook: https://runbooks.cloud-platform.service.justice.gov.uk/creating-a-live-like.html#creating-a-live-like-cluster
Issue 7:
EKS: Upgrade Production clusters to Kubernetes
https://runbooks.cloud-platform.service.justice.gov.uk/upgrade-eks-cluster.html
Production Clusters Checklist:
Issue 8:
Update vpc-cni to latest supported release for upgraded EKS version
Check for the latest supported addon version for the upgraded EKS version and update the clusters
Runbook link
Production Clusters Checklist:
See the Amazon EKS add-ons documentation for more information about addons, or find the latest versions for these EKS add-ons directly:
Issue 9:
Update kube-proxy to latest supported release for upgraded EKS version
Check for the latest supported addon version for the upgraded EKS version and update the clusters
Runbook link
Production Clusters Checklist:
See the Amazon EKS add-ons documentation for more information about addons, or find the latest versions for these EKS add-ons directly:
Issue 10:
Update core-dns to latest supported release for upgraded EKS version
Check for the latest supported addon version for the upgraded EKS version and update the clusters
Runbook link
Production Clusters Checklist:
See the Amazon EKS add-ons documentation for more information about addons, or find the latest versions for these EKS add-ons directly:
Issue 11:
Review cluster components for upgrading
https://runbooks.cloud-platform.service.justice.gov.uk/container-images.html#container-images-used-by-cluster-components
Review the compatibility matrix for all cluster components and verify if the image is compatible with the upgraded Kubernetes version
Issue 12:
Review and upgrade kube-state-metrics for the upgraded EKS version
https://runbooks.cloud-platform.service.justice.gov.uk/container-images.html#container-images-used-by-cluster-components
https://github.com/kubernetes/kube-state-metrics?tab=readme-ov-file#compatibility-matrix
Review the compatibility matrix of kube-state-metrics and verify if the image is compatible with the upgraded Kubernetes version. If the version is a mismatch, check if the whole kube-prometheus-chart needs updating to get the default version of kube-state-metrics from the chart-> values. Otherwise, pin the kube-state-metrics image to match the Kubernetes version.
Issue 13:
Upgrade cluster autoscaler for EKS version
The Cloud Platform EKS Cluster is in Kubernetes version . Hence upgrade the cluster-autoscaler to match the Kubernetes version.
https://github.com/kubernetes/autoscaler/tree/master/charts/cluster-autoscaler
https://github.com/ministryofjustice/cloud-platform-terraform-cluster-autoscaler
Issue 14:
Upgrade cluster descheduler for EKS version
The Cloud Platform EKS Cluster is in Kubernetes version . Hence upgrade the descheduler to match the Kubernetes version.
https://github.com/kubernetes-sigs/descheduler?tab=readme-ov-file#%EF%B8%8F--documentation-versions-by-release
https://github.com/ministryofjustice/cloud-platform-terraform-descheduler
Issue 15:
Post EKS version Cleanup
Following upgrade to EKS , there will be a number of cleanup activities that need addressing:
Update user guide / runbook references to EKS version
Update tools-image for kubectl version
Update cloud-platform-cli for kubectl version
Update concourse pipelines to use updated tools-image and cli
Issue 16:
Update Upgrade runbook and Cluster Upgrade Issue Template
Update the runbook for
Cluster upgrade Runbook:
https://runbooks.cloud-platform.service.justice.gov.uk/upgrade-eks-cluster.html
The text was updated successfully, but these errors were encountered: