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

Update Kubernetes support matrix #1992

Closed
FeynmanZhou opened this issue Dec 19, 2024 · 1 comment · Fixed by #2013
Closed

Update Kubernetes support matrix #1992

FeynmanZhou opened this issue Dec 19, 2024 · 1 comment · Fixed by #2013
Assignees
Labels
dependencies Pull requests that update a dependency file
Milestone

Comments

@FeynmanZhou
Copy link
Collaborator

FeynmanZhou commented Dec 19, 2024

Kubernetes follows an N-2 support policy (meaning that the 3 most recent minor versions receive security and bug fixes) along with a 15-week release cycle. At the end of the day, the most recent three minor Kubernetes releases are 1.32, 1.31, 1.30, which are officially supported by the Kubernetes community.

Looking at the Kubernetes test matrix, Kubernetes v1.29 and v1.30 are covered now. We need to bump up the Kubernetes versions to 1.30 and 1.31 respectively since v1.29 is no longer maintained by Kubernetes community.

In addition, the prerequisite of Ratify installation just mention Kubernetes v1.20 or higher on the website. This is not a strict prerequisite for users. I would suggest adding a supported Kubernetes matrix statement to the installation guide and included the recommended versions (tested by Ratify e2e) there.

@FeynmanZhou FeynmanZhou added the dependencies Pull requests that update a dependency file label Dec 19, 2024
@FeynmanZhou FeynmanZhou added this to the v1.4.0 milestone Dec 19, 2024
@FeynmanZhou
Copy link
Collaborator Author

cc @binbin-li

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants