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-15
Priority: P2
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: charts/kafka-operator/templates/operator-deployment-with-webhook.yaml:10 generates a 365-day certificate; generation at Helm install/upgrade is not automatic renewal.
Proposed Solution
Files: That template, Helm values/schema and chart tests, serving-certificate resources if a new mode is introduced, and installation/upgrade documentation.
Interface contract: Distinguish webhook serving certificates from managed Kafka PKI. Preserve supplied-certificate mode and do not silently make cert-manager a mandatory dependency. Keep serving Secret and webhook CA bundle consistent.
- Choose and document the production renewal mode before implementation: optional cert-manager-managed serving certificate, or another explicitly supported automated mechanism.
- Add chart tests for generated, supplied, and automated modes; validate DNS names, Secret references, CA injection, and upgrade compatibility.
- Exercise certificate rotation with the process running, including trust-bundle transition and an unsuccessful renewal.
- Verify the actual renewal path, not just certificate file hot reload; ensure expiry/renewal failure is observable.
- Validate chart rendering/lint and Kind admission traffic across a deliberately short-lived certificate rotation.
Done when: A supported production mode renews certificates without a Helm upgrade and preserves admission availability.
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-15. 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
New automatic-renewal machinery is removed from active scope under #368. Generated serving certificates still expire after 365 days; #392 retains documenting existing renewal procedures/limitations. This closure does not claim automatic renewal or expiry risk was fixed.