Repository navigation
Description
Implementation status: #395 includes runtime/envtest v0.25.3, the release-aware Kubernetes updater, shared CI pins, and derived-file drift checks. Local make check ENVTEST_K8S_VERSION=1.35.0 and make test ENVTEST_K8S_VERSION=1.37.0 passed. New remote CI and remaining Kind/fault-test requirements are not implied complete.
Delivery bundle: A: Foundation. See #395 and #368 for the four-PR stack.
Parent: #394
Roadmap: #368
Plan item: PR-18
Priority: P2
Dependencies: None
Kubernetes support: Rolling upstream-maintained Kubernetes minors, using the oldest/newest supported boundaries. Current minimum server version: 1.35.0; current test pins: 1.35.0 and 1.37.0. config/kubernetes-versions.env is authoritative. The existing weekly dependency workflow proposes reviewed updates from official release/EOL metadata and common Kind/envtest assets. Normal CI consumes committed pins; metadata failures do not update them. This supersedes the earlier fixed 1.34 minimum; Kubernetes 1.34 reached upstream EOL on October 27, 2026.
Problem Statement
Evidence: Makefile:25 sets setup-envtest to latest; CI/Kind target Kubernetes 1.37.0. Project instructions still cite older runtime/library versions, while PROJECT remains format v2.
Proposed Solution
Files: Makefile, affected go.mod/go.sum files (root, tests/e2e, and third_party/github.com/banzaicloud/operator-tools), .github/workflows/ci.yml, .github/workflows/e2e-test.yaml, .github/actions/kind-create/action.yaml, AGENTS.md, and support/development documentation.
Interface contract: Pin setup-envtest to a verified compatible release and update controller-runtime v0.25.2 to v0.25.3 consistently. The support floor follows the oldest upstream-maintained minor; compatibility jobs use the oldest/newest boundaries from the shared pins, independently of client-library versions. Update, rather than blindly regenerate, legacy project scaffolding.
- Record the rolling upstream support policy, shared version pins, and reviewed automatic updates.
- Centralize CI/envtest/Kind pins and derive the chart/documentation floor; verify drift offline.
- Refresh supported boundaries in the existing weekly dependency workflow using official release/EOL metadata and common stable assets; bound retrieval retries/timeouts and leave pins unchanged on discovery failures.
- Pin tooling and apply the routine runtime patch; preserve Kubernetes module generation alignment and check every affected module.
- Land and verify envtest and Kind E2E CI coverage for the managed oldest/newest upstream-supported boundaries; include fault-injection tests from the other PRs in the appropriate jobs.
- Correct stale contributor instructions and misleading test claims; for example,
TestFinalizerRemovalWithConcurrentUpdatescurrently introduces no concurrent write. - Keep envtest for API semantics and Kind for garbage collection, admission, HA, networking, and actual Kafka behavior.
- Validate with
make check, module-integrity checks, generated-file checks when affected, and the declared server matrix.
Done when: A clean checkout resolves reproducible test tools, documentation matches reality, and compatibility is a tested contract.
Delivery: Four consolidated PRs, approved November 16, 2026: A -> B -> C; D branches from A. Foundation is #395. The 22 PR-XX identifiers are work-item IDs, not separate PRs. Preserve every work-item acceptance criterion and native dependency. No gated experiment is automatically enabled, and no issue is complete merely because one PR references it. D must satisfy its native #375 gate, including lifecycle-domain signals assigned to B; branching from A does not waive that merge prerequisite. Write focused regression tests first; record exact commands/results and run make check plus this issue's real-cluster/measurement gates.
Alternatives Considered
Twenty-two individual PRs add unnecessary integration overhead, while one omnibus PR obscures correctness and rollout boundaries. Deliver this scope in its approved dependency-aligned bundle. Do not expand into deferred consistency, storage, or concurrency changes without their own decision gates.
Support-policy decision updated November 16, 2026: Rolling upstream-maintained minors and managed oldest/newest compatibility boundaries; see #368. The decision-only #381 → #386 blocker is satisfied and removed. Other tooling/schema work remains open and requires its own tests.
Additional Context
Baseline: 95138e0d; detailed roadmap scope: #368, section PR-18. The roadmap #368 and its native sub-issues are the planning source of truth. No planning document is committed in the final PR diffs. Re-read affected source and overlapping work before implementation. Historical baseline test passes are not validation of this change.
Activity
feat(operator): managed Kubernetes support and REST observability (#395)
amuraru commentedon Nov 17, 2026
Foundation/tooling and compatibility work shipped in #395. Under #368, remaining fault/regression validation belongs to its retained owning fixes; this broad umbrella is retired without claiming every original follow-up criterion completed.