Repository navigation
Description
Delivery bundle: B: Lifecycle correctness and status. See #397 and #368 for the four-PR stack.
Parent: #394
Roadmap: #368
Plan item: PR-12
Priority: P2
Dependencies: PR-08
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: KafkaClusterStatus, KafkaTopicStatus, and KafkaUserStatus lack standard conditions and observed-generation attribution.
Proposed Solution
Files: api/v1beta1/kafkacluster_types.go, api/v1alpha1/kafkatopic_types.go, api/v1alpha1/kafkauser_types.go, status/controller helpers/tests, generated deepcopy/CRDs/chart copies, and user documentation.
Interface contract: Add []metav1.Condition with list-map key type; retain existing State fields. Define Ready/Progressing/Degraded meanings and ownership. Each condition attributes the generation it describes; observed generation must not falsely acknowledge an unprocessed spec.
- Add tests for spec changes, failed reconciliation, recovery, unchanged conditions, and concurrent condition writers.
- Assert stable
LastTransitionTimewhen condition status is unchanged and no redundant status write for identical condition content. - Implement conditions using Kubernetes condition helpers and PR-08's safe status mutation pattern.
- Document generation semantics and compatibility with existing status consumers and
kubectl wait. - Run
make generate manifests, API module tests,go test ./controllers ./controllers/tests ./pkg/k8sutil, and verify generated base/chart schemas match.
Done when: Clients can distinguish current-generation readiness from stale historical state.
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-12. 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
Removed from active scope under #368: no demonstrated consumer requirement currently justifies a new conditions/observed-generation API. Retained admission fixes in #394 do not depend on it. No API change claimed.