ci: test Kubernetes 1.36 and 1.37 on devel branch by nixpanic · Pull Request #6550 · ceph/ceph-csi

nixpanic · 2026-09-11T11:43:40Z

Add k8s 1.37 to the test matrix and restrict devel to only
1.36 and 1.37 by excluding 1.32, 1.33, 1.34 and 1.35.
k8s 1.37 is excluded from release-v3.16 and release-v3.17.

Update the Mergify queue conditions to match the updated CI
matrix: only k8s 1.36 and 1.37 are tested on devel, so drop
the 1.34 and 1.35 status-success requirements and add 1.37.

Closes: #6469

mergify · 2026-09-11T11:44:20Z

Merge Protections

🟢 All 2 merge protections satisfied — ready to merge.

Show 2 satisfied protections

🟢 📃 Configuration Change Requirements

Mergify configuration change

any of:
- check-success = @mergify/Configuration changed
- check-success = @mergify/Configuration has been deleted

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

Copilot

🟢 Approval recommended

The CI and Mergify changes are aligned; the remaining documentation mismatch is a minor nit and does not block approval.

Pull request overview

Updates CI to test Kubernetes 1.37 and restrict devel testing to Kubernetes 1.36 and 1.37.

Changes:

Adds Kubernetes 1.37 to the test matrix.
Excludes Kubernetes 1.32–1.35 from devel and 1.37 from release branches.
Updates Mergify queue requirements.

File summaries

File	Summary
`.mergify.yml`	Updates required `devel` CI statuses.
`.github/workflows/pull-request-commentor.yaml`	Adds Kubernetes 1.37 and branch-specific exclusions.

Review details

Suppressed comments (1)

.github/workflows/pull-request-commentor.yaml:22

This changes the devel CI matrix to test only Kubernetes 1.36 and 1.37, but the public “Known to work CO platforms” table still lists devel as tested on 1.34, 1.35, and 1.36 (README.md:61). Please update that row in the same change so the documented support matrix matches the jobs this workflow actually triggers and includes 1.37.

        k8s: ["1.32", "1.33", "1.34", "1.35", "1.36", "1.37"]

Files reviewed: 2/2 changed files
Comments generated: 0
Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

nixpanic · 2026-09-11T11:48:23Z

/test ci/centos/mini-e2e/k8s-1.37/rbd
/test ci/centos/mini-e2e/k8s-1.37/cephfs
/test ci/centos/mini-e2e/k8s-1.37/nvmeof
/test ci/centos/mini-e2e/k8s-1.37/nfs

iPraveenParihar · 2026-09-11T12:43:24Z

/test ci/centos/mini-e2e/k8s-1.37/nfs

nixpanic · 2026-09-11T13:21:49Z

/test ci/centos/mini-e2e/k8s-1.37/nfs

Failed

  [FAIL] nfs Test NFS CSI [It] checking provisioner and nodeplugin are running [acceptance]

(logs)

nixpanic · 2026-09-11T13:25:46Z

/test ci/centos/mini-e2e/k8s-1.37/cephfs

NFS failure:

nfs Test NFS CSI [It] create a PVC clone and bind it to an app [acceptance]

(logs)

nixpanic · 2026-09-14T07:22:08Z

/test ci/centos/mini-e2e/k8s-1.37/cephfs
/test ci/centos/mini-e2e/k8s-1.37/nfs

ceph-csi-bot · 2026-09-14T15:19:18Z

/test ci/centos/k8s-e2e-external-storage/1.34

ceph-csi-bot · 2026-09-14T15:19:18Z

/test ci/centos/k8s-e2e-external-storage/1.36

ceph-csi-bot · 2026-09-14T15:19:19Z

/test ci/centos/mini-e2e/k8s-1.36

ceph-csi-bot · 2026-09-14T15:19:19Z

/test ci/centos/mini-e2e/k8s-1.34

ceph-csi-bot · 2026-09-14T15:19:19Z

/test ci/centos/k8s-e2e-external-storage/1.35

ceph-csi-bot · 2026-09-14T15:19:19Z

/test ci/centos/upgrade-tests-cephfs

ceph-csi-bot · 2026-09-14T15:19:20Z

/test ci/centos/mini-e2e/k8s-1.35

ceph-csi-bot · 2026-09-14T15:19:20Z

/test ci/centos/upgrade-tests-rbd

nixpanic · 2026-09-15T07:27:52Z

@Mergifyio rebase

mergify · 2026-09-15T07:27:56Z

rebase

❌ This pull request comes from a fork and cannot be rebased

Details

GitHub refuses an OAuth token on its rebase API for a fork, so rebasing one means impersonating a GitHub user to force-push the contributor's branch. Mergify does not do that.

Use the update action or the @mergifyio update command instead: it brings the pull request up to date by merging the base branch into it, and needs no impersonation. It only has something to do when the pull request is behind its base branch, so if what the branch needs is a linear history, its author has to rebase it themselves.

nixpanic · 2026-09-15T07:28:09Z

@Mergifyio update

Madhu-1 · 2026-09-15T07:35:05Z

@mergify update

mergify · 2026-09-15T07:35:11Z

update

❌ Pull request can't be updated with latest base branch changes

Details

This pull request seems to come from a fork, and Mergify needs the author's permission to update its branch.
The author needs to enable "Allow edits from maintainers" on this pull request, or update the branch manually.

nixpanic · 2026-09-15T15:09:47Z

@Mergifyio rebase

mergify · 2026-09-15T15:09:57Z

rebase

❌ This pull request comes from a fork and cannot be rebased

Details

GitHub refuses an OAuth token on its rebase API for a fork, so rebasing one means impersonating a GitHub user to force-push the contributor's branch. Mergify does not do that.

Use the update action or the @mergifyio update command instead: it brings the pull request up to date by merging the base branch into it, and needs no impersonation. It only has something to do when the pull request is behind its base branch, so if what the branch needs is a linear history, its author has to rebase it themselves.

nixpanic · 2026-09-15T15:24:49Z

@Mergifyio rebase

mergify · 2026-09-15T15:24:57Z

rebase

❌ This pull request comes from a fork and cannot be rebased

Details

GitHub refuses an OAuth token on its rebase API for a fork, so rebasing one means impersonating a GitHub user to force-push the contributor's branch. Mergify does not do that.

Use the update action or the @mergifyio update command instead: it brings the pull request up to date by merging the base branch into it, and needs no impersonation. It only has something to do when the pull request is behind its base branch, so if what the branch needs is a linear history, its author has to rebase it themselves.

nixpanic · 2026-09-15T17:23:00Z

@Mergifyio update

mergify · 2026-09-15T17:23:08Z

update

❌ GitHub refused to update workflow files

Details

GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/pull-request-commentor.yaml without workflows permission
GitHub only lets Mergify write to .github/workflows/ with the workflows permission. An organization owner can accept Mergify's pending permissions at https://dashboard.mergify.com/repositories?login=ceph.

nixpanic · 2026-09-16T08:30:30Z

Lots of CI jobs failed with NFS issues, #6560 disables the requirement to pass that.

iPraveenParihar · 2026-09-21T05:23:10Z

@Mergifyio rebase

mergify · 2026-09-21T05:23:28Z

rebase

❌ This pull request comes from a fork and cannot be rebased

Details

GitHub refuses an OAuth token on its rebase API for a fork, so rebasing one means impersonating a GitHub user to force-push the contributor's branch. Mergify does not do that.

Use the update action or the @mergifyio update command instead: it brings the pull request up to date by merging the base branch into it, and needs no impersonation. It only has something to do when the pull request is behind its base branch, so if what the branch needs is a linear history, its author has to rebase it themselves.

iPraveenParihar · 2026-09-21T05:23:50Z

@Mergifyio update

mergify · 2026-09-21T05:23:59Z

update

❌ GitHub refused to update workflow files

Details

GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/pull-request-commentor.yaml without workflows permission
GitHub only lets Mergify write to .github/workflows/ with the workflows permission. An organization owner can accept Mergify's pending permissions at https://dashboard.mergify.com/repositories?login=ceph.

iPraveenParihar · 2026-09-21T05:25:40Z

@nixpanic I think you would need to update Mergifyio's permissions or you would need to manually rebase it?

nixpanic · 2026-09-28T11:36:56Z

@nixpanic I think you would need to update Mergifyio's permissions or you would need to manually rebase it?

The Ceph team has accepted the updated permissions for Mergify in the Ceph GitHub Org last week.

@Mergifyio rebase

nixpanic · 2026-09-28T11:37:39Z

@Mergifyio rebase

mergify · 2026-09-28T11:37:46Z

rebase

❌ This pull request comes from a fork and cannot be rebased

Details

GitHub refuses an OAuth token on its rebase API for a fork, so rebasing one means impersonating a GitHub user to force-push the contributor's branch. Mergify does not do that.

Use the update action or the @mergifyio update command instead: it brings the pull request up to date by merging the base branch into it, and needs no impersonation. It only has something to do when the pull request is behind its base branch, so if what the branch needs is a linear history, its author has to rebase it themselves.

nixpanic · 2026-09-28T11:42:44Z

@Mergifyio update

mergify · 2026-09-28T11:42:49Z

update

❌ Pull request can't be updated with latest base branch changes

Details

This pull request seems to come from a fork, and Mergify needs the author's permission to update its branch.
The author needs to enable "Allow edits from maintainers" on this pull request, or update the branch manually.

nixpanic · 2026-09-28T11:43:34Z

@mergify, you're being weird... Whay did you rebase other PRs today?

Add k8s 1.37 to the test matrix and restrict devel to only 1.36 and 1.37 by excluding 1.32, 1.33, 1.34 and 1.35. k8s 1.37 is excluded from release-v3.16 and release-v3.17. Assisted-by: AskBob <askbob@ibm.com> Signed-off-by: Niels de Vos <ndevos@ibm.com>

Update the Mergify queue conditions to match the updated CI matrix: only k8s 1.36 and 1.37 are tested on devel, so drop the 1.34 and 1.35 status-success requirements and add 1.37. Assisted-by: AskBob <askbob@ibm.com> Signed-off-by: Niels de Vos <ndevos@ibm.com>

Pull request has been modified.

iPraveenParihar · 2026-09-29T07:00:23Z

Depends-On: #6582

Copilot AI lite review requested due to automatic review settings September 11, 2026 11:43

nixpanic requested review from a team as code owners September 11, 2026 11:43

Copilot started reviewing on behalf of nixpanic September 11, 2026 11:44 View session

mergify Bot added the component/testing Additional test cases or CI work label Sep 11, 2026

Copilot AI reviewed Sep 11, 2026

View reviewed changes

iPraveenParihar previously approved these changes Sep 11, 2026

View reviewed changes

nixpanic added the ci/skip/multi-arch-build skip building on multiple architectures label Sep 11, 2026

nixpanic mentioned this pull request Sep 11, 2026

update the dependency to kubernetes 1.37 #6525

Open

5 tasks

nixpanic added the ok-to-test Label to trigger E2E tests label Sep 14, 2026

ceph-csi-bot added ci/in-progress/e2e This label acts like a guard and prevents Mergify from adding the `ok-to-test` label again. and removed ok-to-test Label to trigger E2E tests labels Sep 14, 2026

mergify Bot removed the ci/in-progress/e2e This label acts like a guard and prevents Mergify from adding the `ok-to-test` label again. label Sep 14, 2026

nixpanic requested a review from a team September 28, 2026 11:37

nixpanic added 2 commits September 28, 2026 13:44

nixpanic force-pushed the ci/k8s/v1.37 branch from 292171a to df49430 Compare September 28, 2026 11:44

nixpanic requested a review from iPraveenParihar September 28, 2026 11:44

Madhu-1 approved these changes Sep 29, 2026

View reviewed changes

Madhu-1 requested a review from a team September 29, 2026 05:19

iPraveenParihar approved these changes Sep 29, 2026

View reviewed changes

Conversation

nixpanic commented Sep 11, 2026

Uh oh!

mergify Bot commented Sep 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merge Protections

🟢 📃 Configuration Change Requirements

🟢 🚦 Auto-queue

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🟢 Approval recommended

Suppressed comments (1)

Uh oh!

nixpanic commented Sep 11, 2026

Uh oh!

iPraveenParihar commented Sep 11, 2026

Uh oh!

nixpanic commented Sep 11, 2026

Uh oh!

nixpanic commented Sep 11, 2026

Uh oh!

nixpanic commented Sep 14, 2026

Uh oh!

ceph-csi-bot commented Sep 14, 2026

Uh oh!

ceph-csi-bot commented Sep 14, 2026

Uh oh!

ceph-csi-bot commented Sep 14, 2026

Uh oh!

ceph-csi-bot commented Sep 14, 2026

Uh oh!

ceph-csi-bot commented Sep 14, 2026

Uh oh!

ceph-csi-bot commented Sep 14, 2026

Uh oh!

ceph-csi-bot commented Sep 14, 2026

Uh oh!

ceph-csi-bot commented Sep 14, 2026

Uh oh!

nixpanic commented Sep 15, 2026

Uh oh!

mergify Bot commented Sep 15, 2026

❌ This pull request comes from a fork and cannot be rebased

Uh oh!

nixpanic commented Sep 15, 2026

Uh oh!

Madhu-1 commented Sep 15, 2026

Uh oh!

mergify Bot commented Sep 15, 2026

❌ Pull request can't be updated with latest base branch changes

Uh oh!

nixpanic commented Sep 15, 2026

Uh oh!

mergify Bot commented Sep 15, 2026

❌ This pull request comes from a fork and cannot be rebased

Uh oh!

nixpanic commented Sep 15, 2026

Uh oh!

mergify Bot commented Sep 15, 2026

❌ This pull request comes from a fork and cannot be rebased

Uh oh!

nixpanic commented Sep 15, 2026

Uh oh!

mergify Bot commented Sep 15, 2026

❌ GitHub refused to update workflow files

Uh oh!

nixpanic commented Sep 16, 2026

Uh oh!

iPraveenParihar commented Sep 21, 2026

Uh oh!

mergify Bot commented Sep 21, 2026

❌ This pull request comes from a fork and cannot be rebased

Uh oh!

iPraveenParihar commented Sep 21, 2026

Uh oh!

mergify Bot commented Sep 21, 2026

❌ GitHub refused to update workflow files

Uh oh!

iPraveenParihar commented Sep 21, 2026

mergify Bot commented Sep 11, 2026 •

edited

Loading