villebro opened a new pull request, #77: URL: https://github.com/apache/superset-kubernetes-operator/pull/77
E2E previously ran against a single, unpinned `kindest/node:v1.35.1` tag — a version not actually published by kind v0.31.0 and not reflected in any user-facing support statement. This PR pins e2e to a digest-locked matrix of the two newest Kubernetes minors that kind ships node images for (currently 1.35 + 1.34), adds a non-blocking lane for the newest Kubernetes release that kind hasn't yet bundled (currently 1.36, built locally via `kind build node-image --type release`), and surfaces the supported versions in `README.md` and the installation docs from a single JSON source of truth — enforced by a drift check. ## Details - `.github/supported-k8s.json` is the single source for both the CI matrix and the rendered docs table. Digests verified against the [kind v0.31.0 release notes](https://github.com/kubernetes-sigs/kind/releases/tag/v0.31.0). - `.github/workflows/test.yaml`: - New `e2e-matrix` job emits the JSON as a matrix via `jq -c .`. - `e2e` job is now matrixed (`fail-fast: false`), with `KIND_CLUSTER: superset-op-e2e-${{ matrix.k8s.minor }}` to avoid cross-leg collisions. - New `e2e-next` job runs against `v1.36.0` built locally; `continue-on-error: true` so it doesn't block PRs while kind's bundled kubeadm config trails a new minor. - Kind install stays curl + `sha256sum -c` (Renovate-managed, lockstep version + checksum bump). - `scripts/render-supported-versions.sh` (bash + jq + awk) writes the table between `<!-- BEGIN SUPPORTED-K8S -->` / `<!-- END SUPPORTED-K8S -->` sentinels in `README.md` and `docs/user-guide/installation.md`. Hand-written policy paragraph lives outside the sentinels. - `Makefile`: `KIND_NODE_IMAGE` default switched to the digest-pinned 1.35.0 image (matches the first JSON entry); `supported-versions` and `verify-supported-versions` targets added; `supported-versions` wired into the `codegen` aggregate. - `.github/workflows/ci.yaml`: dedicated `verify-supported-versions` job so stale tables produce a clear PR-level failure signal. - `.asf.yaml`: adds `Verify supported-versions table` to required status checks. The pre-existing `E2E` check was not required, so renaming it to `E2E (1.35)` / `E2E (1.34)` introduces no regression. - `renovate.json`: two `customManagers` — kindest/node digests in the JSON (docker datasource) and `KIND_VERSION` + `KIND_CHECKSUM` in workflows (github-releases datasource, lockstep update for `kubernetes-sigs/kind`). - `.rat-excludes`: header-less JSON file excluded. When kind ships a release covering 1.36 (expected in kind v0.32.0): bump the `KIND_VERSION`/`KIND_CHECKSUM` pair, update the JSON to `[1.36, 1.35]`, retarget `K8S_NEXT` to the next-newest minor, then `make codegen`. Integration tests still use envtest derived from `k8s.io/api`. Matrixing `ENVTEST_K8S_VERSION` is intentionally out of scope. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
