8000 fix(e2e): set required spec.stability on KinD E2E Component CRs by VLukiantsev · Pull Request #1564 · google/xmc · GitHub
[go: up one dir, main page]

Skip to content

fix(e2e): set required spec.stability on KinD E2E Component CRs - #1564

Merged
VLukiantsev merged 1 commit into
mainfrom
fix/kind-e2e-component-stability
Nov 3, 2026
Merged

VLukiantsev merged 1 commit into
mainfrom
fix/kind-e2e-component-stability

Conversation

@VLukiantsev
Copy link
Copy Markdown
Collaborator

Summary

Fixes the KinD & Playwright Headless E2E failure on main by setting the now-required spec.stability field on Component CRs applied by the E2E suites.

Motivation & Context

#1540 made spec.stability a required field (enum EXPERIMENTAL/PREVIEW/STABLE) in the Component CRD. The Playwright E2E stage [6/6] Verifying Authenticated xmc-bridge -> CMS Reconciliation applies an inline e2e-cms-auth-check Component without it, so the API server rejects it:

The Component "e2e-cms-auth-check" is invalid:
* spec.stability: Required value

Failing run: https://github.com/google/xmc/actions/runs/41634507535/job/125914638219

The Go KinD harnesses install the same CRD from deploy/helm/templates/components/crd.yaml and build Component specs without stability, so they are fixed in the same PR.

Key Changes

  • test/e2e/test_e2e_flow.py: add "stability": "STABLE" to the e2e-cms-auth-check Component manifest.
  • test/e2e/components_lifecycle_e2e_test.go: add stability: STABLE in applyLifecycleComponent.
  • test/e2e/kind_3p_harness_test.go: add stability: STABLE to the 3P wrapper Component spec.

Assumptions

  • STABLE is the right tier for these test fixtures — it avoids the acknowledgeExperimental CEL rule and CMS STABILITY_INVERSION checks, which these tests do not target — if wrong, stability-specific coverage would need dedicated test cases instead.
  • Rendered-manifest examples in deploy/profiles/stable-2026a/components/{clickhouse,redpanda}/README.md also omit stability; left out of scope as doc drift unrelated to the CI failure.
  • The full KinD E2E suite was not re-run locally (requires KinD + Spanner); the merge_group run is the verification.

Verification & Testing

  • Commands Executed: bazel build //test/e2e:components_lifecycle_test //test/e2e:kind_3p_harness_unit_test, bazel test //test/e2e:kind_3p_harness_unit_test, ./.githooks/pre-commit
  • Coverage & Test Status: Build succeeds; kind_3p_harness_unit_test passes; pre-commit hooks pass.

Related Issues / Bugs

N/A

TAG=agy
CONV=076b9660-2c35-402b-bd1f-2beb667902d7

#1540 made spec.stability a required field in the Component CRD. The
Playwright E2E CMS reconciliation check and the Go KinD harnesses apply
Component CRs without it, which the API server now rejects
("spec.stability: Required value"), breaking the KinD & Playwright
Headless E2E merge-queue job.

Set stability to STABLE on these test fixtures; STABLE avoids the
acknowledgeExperimental CEL rule and CMS STABILITY_INVERSION checks
which these tests do not target.

TAG=agy
CONV=076b9660-2c35-402b-bd1f-2beb667902d7
@gemini-code-assist gemini-code-assist Bot left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request updates several end-to-end test files, including components_lifecycle_e2e_test.go, kind_3p_harness_test.go, and test_e2e_flow.py, to include a "stability": "STABLE" field in the component specifications. There are no review comments to address, and I have no additional feedback to provide.

@VLukiantsev
VLukiantsev marked this pull request as ready for review November 3, 2026 13:16
@VLukiantsev
VLukiantsev enabled auto-merge November 3, 2026 13:16
@VLukiantsev VLukiantsev added the priority::1-critical needs to be review and merged quickly. label Nov 3, 2026
@VLukiantsev
VLukiantsev added this pull request to the merge queue Nov 3, 2026
Merged via the queue into main with commit 05aa779 Nov 3, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority::1-critical needs to be review and merged quickly.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0