Skip to content

fix(ci): pin the k8s E2E cluster name (#1040) - #1042

Merged
RonaldHensbergen merged 1 commit into
mainfrom
fix/1040-k8s-e2e-cluster-name
Oct 31, 2026
Merged

RonaldHensbergen merged 1 commit into
mainfrom
fix/1040-k8s-e2e-cluster-name

Conversation

@RonaldHensbergen

Copy link
Copy Markdown
Owner

Closes #1040.

Follow-up from the #1027 review: the CI checkout is a detached HEAD, so k3d-env.sh's branch-derived default named the cluster cds-head. This pins CDS_CLUSTER: cds-k8s-e2e-ci in the job env (with a comment explaining why), pins the invariant in tests/test_k8s_e2e_workflow.py, and adds a CHANGELOG entry.

Verified locally: full suite 1972 passed / 24 skipped, ruff and yamllint clean. The workflow itself changes, so the k8s E2E job runs on this PR and will show the new cluster name in its make k3d-down step.

The CI checkout is a detached HEAD, so the branch-derived default in
k3d-env.sh named the cluster "cds-head". Pin CDS_CLUSTER to
"cds-k8s-e2e-ci" in the job env for attributable logs and diagnostics,
and pin the invariant in test_k8s_e2e_workflow.py.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
@sonarqubecloud

Copy link
Copy Markdown

@RonaldHensbergen RonaldHensbergen left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Self-review (contributor == reviewer), all angles checked.

Blocking: none.
Major: none.
Minor: none.

Verified beyond the diff itself:

  • Runtime proof, not just green rendering: the E2E job log on this very commit shows creating cluster cds-k8s-e2e-ci and deleting cluster cds-k8s-e2e-ci — the fix works at runtime, not only in YAML.
  • All 14 checks green on b652c8b, including the k3d E2E job (4m35s) and SonarCloud.
  • Full suite locally: 1972 passed / 24 skipped; ruff and yamllint clean.
  • CHANGELOG [Unreleased] Fixed entry present; no E-/W-codes added, so no README troubleshooting or code-collision impact; minimal 3-file diff.

Conclusion: no loose ends or gaps remain for this PR; in my judgment it is merge-ready.

Comment thread .github/workflows/k8s-e2e.yml Resolved
Comment thread tests/test_k8s_e2e_workflow.py Resolved
Comment thread CHANGELOG.md Resolved

Copy link
Copy Markdown
Owner Author

Housekeeping: all 3 review threads are now answered and resolved — no openstaande punten meer. Re-verified on b652c8b: tests/test_k8s_e2e_workflow.py 5 passed locally, ruff clean, all 14 CI checks green incl. SonarCloud and the k3d E2E job (cluster cds-k8s-e2e-ci visible in its logs). In my judgment this PR is merge-klaar; the only remaining gate is the requested review from @SemTiOne (branch protection requires 1 approving review).

@RonaldHensbergen
RonaldHensbergen merged commit 3ef8279 into main Oct 31, 2026
14 checks passed
@RonaldHensbergen
RonaldHensbergen deleted the fix/1040-k8s-e2e-cluster-name branch October 31, 2026 12:56

Copy link
Copy Markdown
Owner Author

Admin-merged by RonaldHensbergen at 2026-10-31T12:56:24Z (merge commit 3ef8279), bypassing the pending review request from @SemTiOne (branch protection requires 1 approving review; enforce_admins is off).

Quality judgment given before the admin merge: merge-klaar — all 14 CI checks green on b652c8b (incl. SonarCloud gate and the k3d E2E job showing cluster cds-k8s-e2e-ci), tests/test_k8s_e2e_workflow.py 5 passed locally on the PR branch, ruff clean, self-review found no blocking/major/minor items, all 3 review threads answered and resolved, minimal 3-file diff (+14) matching #1040. Closes #1040.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

k8s-e2e workflow: pin the CI cluster name instead of the derived cds-head

1 participant