ci: start testing the devel branch with Kubernetes 1.35#5973
Conversation
There is no need to test the devel branch with Kubernetes 1.32 anymore. Current release branches will not change their tested Kubernetes versions. Signed-off-by: Niels de Vos <ndevos@ibm.com>
Signed-off-by: Niels de Vos <ndevos@ibm.com>
Release v3.17.0 is still a bit away, but we're only testing the devel branch with a limited number of Kubernetes versions. Signed-off-by: Niels de Vos <ndevos@ibm.com>
|
/test ci/centos/mini-e2e-operator/k8s-1.35 |
|
/test ci/centos/mini-e2e-helm/k8s-1.35 |
|
/test ci/centos/mini-e2e/k8s-1.35 |
|
/test ci/centos/k8s-e2e-external-storage/1.35 |
|
/test ci/centos/k8s-e2e-external-storage/1.32 |
|
/test ci/centos/k8s-e2e-external-storage/1.34 |
|
/test ci/centos/mini-e2e-helm/k8s-1.32 |
|
/test ci/centos/k8s-e2e-external-storage/1.33 |
|
/test ci/centos/upgrade-tests-cephfs |
|
/test ci/centos/mini-e2e/k8s-1.32 |
|
/test ci/centos/mini-e2e-helm/k8s-1.34 |
|
/test ci/centos/mini-e2e/k8s-1.34 |
|
/test ci/centos/upgrade-tests-rbd |
|
/test ci/centos/mini-e2e-helm/k8s-1.33 |
|
/test ci/centos/mini-e2e/k8s-1.33 |
|
@nixpanic, all tests have passed. I’ll add the skip-ci label to avoid unnecessary runs. |
|
@Mergifyio queue |
✅ The pull request has been merged automaticallyDetailsThe pull request has been merged automatically at 63bdf50 |
Merge Queue Status✅ The pull request has been merged at 4565877 This pull request spent 5 minutes 38 seconds in the queue, including 5 minutes 24 seconds running CI. Required conditions to merge
|
There is no need to test the devel branch with Kubernetes 1.32 anymore.
Current release branches will not change their tested Kubernetes
versions.
The
ok-to-testlabel still comments with the previous version of theworkflow. It uses the one that is available in the
develbranch.Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>: retest the<job-name>after unrelatedfailure (please report the failure too!)