Add planning and updating runbook steps

.github/ISSUE_TEMPLATE/cloud-platform-k8s-upgrade-template.md

@@ -5,6 +5,26 @@ label: 'EPIC'
 ---
 
 ## Issue 1:
+### Planning upgrade to EKS <version>
+
+Go through the release notes of EKS 1.27 and create a plan to upgrade our clusters
+
+Things to consider:
+
+Review changelog & release notes
+EKS Module support at current version?
+Are there any API deprecations & removals? (Check 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 <version>?
+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 from <current-version> to the version needed for current k8s version
 Check for the latest supported addon version for the current kubernetes version and update the clusters
 
@@ -21,7 +41,7 @@ See the [Amazon EKS add-ons](https://docs.aws.amazon.com/eks/latest/userguide/ek
 - [vpc-cni](https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html)
 
 
-## Issue 2:
+## Issue 3:
 ### Update kube-proxy from <current-version> to the version needed for current k8s version
 Check for the latest supported addon version for the current kubernetes version and update the clusters
 
@@ -38,7 +58,7 @@ See the [Amazon EKS add-ons](https://docs.aws.amazon.com/eks/latest/userguide/ek
 - [vpc-cni](https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html)
 
 
-## Issue 3:
+## Issue 4:
 ### Update core-dns from <current-version> to the version needed for current k8s version
 Check for the latest supported addon version for the current kubernetes version and update the clusters
 
@@ -54,17 +74,17 @@ See the [Amazon EKS add-ons](https://docs.aws.amazon.com/eks/latest/userguide/ek
 - [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)
 
-## Issue 4:
+## Issue 5:
 ### Test EKS <version> on test cluster
 
 Follow instructions from Upgrade runbook: https://runbooks.cloud-platform.service.justice.gov.uk/upgrade-eks-cluster.html#upgrade-eks-cluster
 
-## Issue 5:
+## Issue 6:
 ### Test EKS <version> 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 6:
+## Issue 7:
 ### EKS: Upgrade Production clusters to Kubernetes <version>
 https://runbooks.cloud-platform.service.justice.gov.uk/upgrade-eks-cluster.html
 
@@ -74,7 +94,7 @@ Production Clusters Checklist:
 - [ ] manager
 - [ ] live
 
-## Issue 7:
+## Issue 8:
 ### Update vpc-cni from <version> to the version needed for the upgraded k8s version
 Check for the latest supported addon version for the upgraded kubernetes version and update the clusters
 
@@ -91,7 +111,7 @@ See the [Amazon EKS add-ons](https://docs.aws.amazon.com/eks/latest/userguide/ek
 - [vpc-cni](https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html)
 
 
-## Issue 8:
+## Issue 9:
 ### Update kube-proxy from <version> to the version needed for the upgraded k8s version
 Check for the latest supported addon version for the upgraded kubernetes version and update the clusters
 
@@ -108,7 +128,7 @@ See the [Amazon EKS add-ons](https://docs.aws.amazon.com/eks/latest/userguide/ek
 - [vpc-cni](https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html)
 
 
-## Issue 9:
+## Issue 10:
 ### Update core-dns from <version> to the version needed for the upgraded k8s version
 Check for the latest supported addon version for the upgraded kubernetes version and update the clusters
 
@@ -124,39 +144,50 @@ See the [Amazon EKS add-ons](https://docs.aws.amazon.com/eks/latest/userguide/ek
 - [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)
 
-## Issue 10:
+## 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 kuebrnetes version
 
-## Issue 11:
+## Issue 12:
 ### Review and upgrade kube-state-metrics for the upgraded cluster version <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 kuebrnetes version. If the version is 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 12:
+## Issue 13:
 ### Upgrade cluster autoscalar for k8s version <version>
 The Cloud Platform Cluster is in k8s version <version>. Hence upgrade the cluster-autoscalar to match the k8s version.
 
 https://github.com/kubernetes/autoscaler/tree/master/charts/cluster-autoscaler
 https://github.com/ministryofjustice/cloud-platform-terraform-cluster-autoscaler
 
-## Issue 13:
+## Issue 14:
 ### Upgrade cluster descheudler for k8s version <version>
 The Cloud Platform Cluster is in k8s version <version>. Hence upgrade the descheduler to match the k8s 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 14:
+## Issue 15:
 ### Post k8s version <version> Cleanup
 Following upgrade from EKS <old-version > <version>, there will be a number of cleanup activities that need addressing:
 
 Update user guide / runbook references
 Update tools-image for kubectl version
 Update cloud-platform-cli for kubectl version 
-Update concourse pipelines to use updated tools-image and cli
+Update concourse pipelines to use updated tools-image and cli
+
+## Issue 16:
+### Update Upgrade runbook and 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
+- any changes to the upgrade issue template
+
+Cluster upgrade Runbook:
+https://runbooks.cloud-platform.service.justice.gov.uk/upgrade-eks-cluster.html