SPIKE: any breaking changes in k8s upgrade?

[sfreudenthaler]

Parent Issue

#30787

Questions

Produce some documentation for

• What version would we target?
  • What's the latest version supported on all of our EKS cluster
  • Is it the latest version (v1.31.3) of k8s?
• Can we hop directly to that version from the one we're on?
• Is there anything in the changelog that we're worried will break?

[cobbg]

The latest EKS version available is v1.31. EKS does not use revision versions like Kubernetes versions, such as v1.31.3. As such, we will be targeting upgrading our EKS clusters to v1.31.

Our clusters are currently running v1.29 and we cannot upgrade directly to 1.31. EKS upgrades must be performed incrementally, so we will need to upgrade to 1.30 and then 1.31. Fortunately, this can be done relatively quickly and we can just perform back-to-back upgrades.

There has been nothing identified in the change logs for either version that we would expect to break or otherwise cause problems. We have since upgraded our internal clusters to 1.31 without any significant problems. The only thing that was identified is the need to upgrade some older versions of Kube Proxy to be compatible with 1.30, which is identified in EKS Upgrade Insights. The process for this upgrade is quick and easy.

[cobbg]

Because these questions have been answered in my previous comment and the actual work to upgrade internal clusters and prod clusters is being tracked in other issues, I'm going to mark this issue as done.