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

In May 2023 (or before z2jh 3.0.0 release?) - drop support for k8s 1.22 #3040

Closed
consideRatio opened this issue Feb 28, 2023 · 0 comments · Fixed by #3092
Closed

In May 2023 (or before z2jh 3.0.0 release?) - drop support for k8s 1.22 #3040

consideRatio opened this issue Feb 28, 2023 · 0 comments · Fixed by #3092

Comments

@consideRatio
Copy link
Member

consideRatio commented Feb 28, 2023

This is an issue to help us remember the policy (see #2591, #2979) to allow ourselves to drop support for k8s versions as long as major cloud providers has stopped supporting them.

k8s GKE EOL EKS EOL AKS EOL Comment
1.22 28 Feb 2023 01 May 2023 Dec 2022 We can dro support 01 May 2023
1.23 31 May 2023 01 Oct 2023 Apr 2023 We can drop support 01 Oct 2023

I suggest drop support as part of the z2jh 3.0.0 release if it happens before 01 May. At worst someone will be forced to upgrade the k8s cluster a month or so before it reached EOL in the managed cloud provider service if they want to update to the new z2jh version directly as well.

The key benefit of dropping a bit earlier is that we reduce complexity for maintenance of this helm chart, and that we avoid making another breaking release.

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

Successfully merging a pull request may close this issue.

1 participant