Skip to content

Admission and dependency-triggered convergence correctness #394

Open
4 of 4 issues completed
Open

Description

@amuraru

Outcome

Irrelevant metadata updates avoid unnecessary Kafka admission dependencies, while relevant Kubernetes dependency changes cause convergence. Consolidates #379/#382 under #368.

Scope and acceptance

  • Reproduce Kafka admin calls on finalizer/irrelevant-label updates, then skip external checks when validation-relevant inputs are unchanged.
  • Preserve validation for spec changes, adoption, and managedBy transitions. Keep current fail-closed semantics for retained external checks; do not move availability checks asynchronously.
  • Bound/cancel retained checks where supported by the actual client path. Do not depend on a repository-wide context refactor or new conditions API.
  • Reproduce a dependency-only event that fails to converge, then add only the required watch/predicate/index mapping. Cover relevant readiness/Secret/recovery behavior without unrelated fanout or making optional CRDs mandatory.

Limits

No blanket watch cleanup, new external-drift polling, conditions, CEL relocation, admission-contract change, or new atomic uniqueness mechanism. Cached duplicate checks do not prove atomic uniqueness.

Historical children are superseded, not implemented. #380/#381/#389 are removed from active scope; their old acceptance criteria are not hidden prerequisites.

Validation

Focused failing request-count, outage, adoption, and dependency-event tests; existing controller/webhook/envtest tests and make check. Use real webhook admission in Kind for affected outage/finalization behavior. Record exact results and unrun checks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions