Repository navigation
Description
Delivery bundle: D: HA and secure deployment. See #395 and #368 for the four-PR stack.
Parent: #392
Roadmap: #368
Plan item: PR-05
Priority: P1
Dependencies: None
Kubernetes support: Rolling upstream-maintained minors; use the oldest/newest boundaries pinned in config/kubernetes-versions.env. See #368 for the current policy. Unrun jobs are not passed validation.
Problem Statement
Evidence: main.go:133-136 hashes raw namespace text although cache configuration trims names. Equivalent or overlapping scopes can use different leases.
Proposed Solution
Files: main.go, focused manager-configuration tests (create main_test.go if needed), Helm values/schema/templates, and deployment documentation.
Interface contract: One canonical representation of a namespace set is used for cache scope and election identity. Empty scope means all namespaces. Define and document how installation scope, lease namespace, and installation identity prevent overlapping ownership.
- Add namespace parsing tests for reordering, whitespace, duplicate names, empty/all-namespace scope, and invalid mixed empty entries.
- Record the maintainer-approved overlapping-installation policy before implementation: explicit installation identity with disjoint ownership, or unsupported/rejected overlap. Do not claim namespace sorting detects every overlap.
- Canonicalize scope and implement the chosen policy. Cover deployments in different operator namespaces as well as identical namespace sets.
- Write and exercise a lease-identity migration procedure that never runs old and new lock domains concurrently; do not ship a naive rolling lock rename.
- Validate with focused manager configuration tests, chart rendering tests, and a two-installation Kind rollout/failover test.
Done when: Equivalent scopes behave identically and both overlap restrictions and lock migration are explicit and tested.
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.
Additional Context
Baseline: 95138e0d; detailed roadmap scope: #368, section PR-05. 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
amuraru commentedon Nov 17, 2026
Equivalent-scope leader identity and safe migration are consolidated into #392 under #368. No new installation-ownership framework or claim that sorting solves arbitrary overlaps. Superseded, not implemented.