-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Add Minimum and Maximum kubernetes version for the releases. #13632
Comments
This is a common question, sounds good to clarify in the docs. Currently in
I'm thinking this format:
Instead of trying to create a table of all K8s versions fo previous Rook versions, the K8s versions indicates approximately 6 K8s versions are supported from the min version. The K8s versions tested in previous versions may also be reconstructed from the history of .mergify.yml. For example, in the release-1.8 branch, we see that the min and max version of K8s tested were v1.16 and v1.22:
|
That would be great. |
@travisn |
@parth-gr Frequently it is rounded up to the 7th release if a K8s release comes out around the time of the Rook release. |
Okay |
The docs for 1.12 and 1.13 have been updated. Going forward we will also document this in future releases. For support versions in previous releases, please see the versions tested as defined in the .mergify config. |
Is this a bug report or feature request?
What should the feature do:
Update the documentation with a table showing rook releases and their kubernetes version support. The older documentations just state the minimum version with no maximum version.
What is use case behind this feature:
Environment:
The text was updated successfully, but these errors were encountered: