Skip to content
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

Upgrade Kubernetes (K8s) version to 1.25 #2464

Open
mieszko4 opened this issue Jan 10, 2025 · 1 comment
Open

Upgrade Kubernetes (K8s) version to 1.25 #2464

mieszko4 opened this issue Jan 10, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@mieszko4
Copy link

mieszko4 commented Jan 10, 2025

Description

Upgrade Kubernetes (K8s) version to at least 1.25

Motivation

Currently the project uses 1.22 which is not supported by AWS anymore.
It was possible to automatically upgrade it on AWS EKS to 1.24, however, it is not possible to do that for 1.25.

AWS will drop the support for older K8s at the end of the month:

Your cluster's Kubernetes version (1.24) will reach the end of extended support in less than one month. Upgrade your Kubernetes cluster to a supported version before January 31, 2025. If you don't, your cluster will be automatically upgraded to Kubernetes version 1.25.

Additional context

Automatic upgrade on EKS is not possible because of 2 errors in EKS Upgrade insights:

  1. EKS add-on version compatibility
  • Description: Checks version of installed EKS add-ons to ensure they are compatible with the next version of Kubernetes.
  • Action: Upgrade your EKS add-on to a newer version compatible with the next Kubernetes version.
  • Deprecation details: None
  1. Deprecated APIs removed in Kubernetes v1.25
  • Description: Checks for usage of deprecated APIs that are scheduled for removal in Kubernetes v1.25. Upgrading your cluster before migrating to the updated APIs supported by v1.25 could cause application impact.
  • Action: Update manifests and API clients to use newer Kubernetes APIs if applicable before upgrading to Kubernetes v1.25. Migrate from Pod Security Policy (PSP) to an alternative approach such as Pod Security Standards or an admission controller.
  • Deprecation details:
image
@mieszko4 mieszko4 added the enhancement New feature or request label Jan 10, 2025
@mieszko4
Copy link
Author

There is a fork with 1.26 upgrade -> #2458

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant