CI: use kubernetes 1.25 For E2E (backport #3473) #3480
Conversation
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
As we need to test with last 3 Kubernetes releases removing Kubernetes 1.22 as we have 1.23, 1.24 and 1.25 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> (cherry picked from commit 4039bf5)
As we have successful runs with kubernetes 1.25 Marking is as default for CI jobs and required for merging PR. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> (cherry picked from commit f19805a)
|
is this really needed? are workflows/actions and the Mergify configuration not taken from the devel branch? |
mergify will be from the devel branch, but from my testing, GitHub action will run from a specific branch, not from the devel branch. let's keep it open, if its not required close it or merge it. |
|
PR is already merged in devel branch, lets use this PR for testing 🗡️ |
|
/test ci/centos/k8s-e2e-external-storage/1.22 |
|
/test ci/centos/k8s-e2e-external-storage/1.23 |
|
/test ci/centos/k8s-e2e-external-storage/1.24 |
|
/test ci/centos/mini-e2e-helm/k8s-1.22 |
|
/test ci/centos/mini-e2e-helm/k8s-1.23 |
|
/test ci/centos/mini-e2e-helm/k8s-1.24 |
|
/test ci/centos/mini-e2e/k8s-1.22 |
|
/test ci/centos/mini-e2e/k8s-1.23 |
|
/test ci/centos/mini-e2e/k8s-1.24 |
|
/test ci/centos/upgrade-tests-cephfs |
|
/test ci/centos/upgrade-tests-rbd |
|
Look at the test result https://github.com/ceph/ceph-csi/actions/runs/3346491014/jobs/5543364554, it's not considering GitHub action from the devel branch (No 1.25 tests were started) |
Madhu-1
added
ci/skip/e2e
|
/test ci/centos/mini-e2e-helm/k8s-1.25 |
|
/test ci/centos/mini-e2e/k8s-1.25 |
|
/test ci/centos/k8s-e2e-external-storage/1.25 |
This is an automatic backport of pull request #3473 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com