-
Notifications
You must be signed in to change notification settings - Fork 78
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
rook 1.13.10 #5581
rook 1.13.10 #5581
Conversation
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5581-15fc1db-rook-1.13.10-k8s-docker-2025-02-17T21:41:28Z |
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5581-1e902b0-rook-1.13.10-k8s-docker-2025-02-17T22:07:27Z |
@@ -11,7 +11,7 @@ KURL_BIN_UTILS_FILE= | |||
# STEP_VERSIONS array is generated by the server and injected at runtime based on supported k8s versions | |||
STEP_VERSIONS=(0.0.0 0.0.0 0.0.0 0.0.0 0.0.0 0.0.0 0.0.0 0.0.0 0.0.0 0.0.0 0.0.0 0.0.0 0.0.0 0.0.0 0.0.0 0.0.0 1.16.4 1.17.13 1.18.20 1.19.16 1.20.15 1.21.14 1.22.17 1.23.17 1.24.17 1.25.14 1.26.15 1.27.16 1.28.15 1.29.14 1.30.10 1.31.6 1.32.2) | |||
# ROOK_STEP_VERSIONS array is generated by the server and injected at runtime based on supported rook versions | |||
ROOK_STEP_VERSIONS=(1.0.4-14.2.21 0.0.0 0.0.0 0.0.0 1.4.9 1.5.12 1.6.11 1.7.11 1.8.10 1.9.12 1.10.11 1.11.8 1.12.8) | |||
ROOK_STEP_VERSIONS=(1.0.4-14.2.21 0.0.0 0.0.0 0.0.0 1.4.9 1.5.12 1.6.11 1.7.11 1.8.10 1.9.12 1.10.11 1.11.8 1.12.8 1.13.10 1.14.12 1.15.8 1.16.3) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm adding the 1.14/1.15/1.16 versions here so that it's easier to test upgrades to them in the dev work that will immediately follow this
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5581-8886de2-rook-1.13.10-k8s-docker-2025-02-17T23:21:01Z |
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Steps to reproduce
Does this PR introduce a user-facing change?
Does this PR require documentation?