Repository navigation
Description
Scope
Scope reduced with maintainer approval on November 17, 2026. Retain demonstrable correctness/availability fixes in existing supported configurations, plus performance work justified by measurements. Preserve existing architecture and deployment modes.
This replaces the 22-item acceptance matrix and mandatory four-PR stack. Closed historical children are superseded or explicitly removed from active work, not all implemented.
Active outcomes
- Lifecycle safety: cleanup ownership, bounded deletion, and result persistence #391: lifecycle safety and necessary cancellation/status fixes.
- Admission and dependency-triggered convergence correctness #394: safe admission fast paths and reproduced dependency-convergence fixes.
- Serving correctness: alert routing, readiness, and proxy wiring #392: serving correctness in existing deployment modes.
- Measured efficiency: avoid redundant writes and unrelated operation scans #393: measured reductions in redundant writes and unrelated operation retrieval; blocks no correctness fix.
Deliver small, coherent PRs per outcome. No requirement for one PR per historical issue or for the old broad bundle stack. #397 remains open; no merge is authorized by this scope revision.
Delivered
#395 delivered tooling/runtime alignment, rolling Kubernetes support, REST-client instrumentation, and CI/E2E boundaries at 1.35.0/1.37.0. Use config/kubernetes-versions.env as the current version source. #398 delivered the related Renovate configuration fix.
#397 contains the Cruise Control result-persistence fix, including conflict-only direct GETs in f022f619; it is not merged. Additional finalizer work is local/uncommitted, not part of its published scope.
Removed from active work
No measured requirement currently justifies cache tuning (#377), conditions (#380), CEL relocation (#381), warmup (#387), SSA (#388), new drift-polling behavior (#389), or higher concurrency (#390).
Do not add new automatic certificate-renewal machinery (#383). Generated serving certificates still expire after 365 days; retain the limitation and document the existing renewal procedure. This is not a claim that automatic renewal is implemented.
The REST portion of #375 shipped. Drop its mandatory domain-metrics/Events/dashboard framework; use existing signals and add instrumentation only where a retained fix requires it. Foundation follow-up validation from #386 belongs to each affected fix, not an indefinitely open umbrella.
Reopen a narrow item only for a demonstrated failure, actual consumer/operational requirement, or worthwhile measured benefit. Do not retain experiments merely to use newer framework features.
Guardrails
Preserve rollout/quorum/draining/storage retention, topic adoption and management modes, supplied/shared Secrets, optional integrations, and execution-critical freshness. Retry persistence without resubmitting external work; no exactly-once or submit-then-crash adoption guarantee.
No repository-wide context/status rewrite, new ownership framework, metrics architecture, certificate mode, or tuning switches. Namespace canonicalization requires a safe lease migration and does not solve arbitrary overlapping installations. Coordinate alert changes with #365.
Add focused failing regressions, use existing tests/linters and make check, and exercise affected real admission/GC/routing/failover behavior in Kind. Measurements do not block correctness fixes. Preserve the PR template and keep bodies terse, with exact validation results and essential caveats.
Activity
21 remaining items
feat(operator): managed Kubernetes support and REST observability (#395)
[-]Modernize operator lifecycle, HA, and efficiency using upstream controller-runtime guidance[/-][+]Operator correctness and measured efficiency[/+]