Skip to content

Lifecycle safety: cleanup ownership, bounded deletion, and result persistence #391

Open
4 of 4 issues completed

Description

@amuraru

Outcome

External work retains its cleanup ownership and recorded result; deletion cannot occupy a worker indefinitely. Consolidated under #368 from #369/#370/#372 and necessary parts of #371/#376.

Scope and acceptance

  • Persist a submitted Cruise Control result across status conflicts without resubmitting external work. Keep the first write free of a direct GET; refresh only for conflict retries. Preserve task/UID guards, retry history, and stop selection. Published in open fix(controllers): persist Cruise Control results across conflicts #397, not merged.
  • Persist required finalizers/discoverable cleanup identity before protected provisioning. Cover write failure, deletion during provisioning, and restart after side effects. Preserve unmanaged-topic behavior and external/shared Secrets. Review existing uncommitted work against these failures before shipping it.
  • Submit topic deletion and observe/requeue until absence; retain the finalizer while pending. Prove disabled/stalled deletion does not hold a worker indefinitely and restart remains safe.
  • Add cancellation only where a retained blocking path needs it. Topic deletion is not blocked by a repository-wide component-interface migration.
  • Fix additional status-conflict/ownership failures only with a focused reproduction. Preserve unrelated writers and avoid replaying stale whole status.

Limits

No blanket context/status rewrite, new timeout-configuration subsystem, conditions, or domain-metrics framework. No automatic external-task adoption or exactly-once guarantee.

Historical child issues were closed as superseded, not completed. This issue's checklist is authoritative; old child-count completion and blocker edges do not establish that these outcomes are done.

Validation

Observe RED/GREEN for retained failures. Use affected controller/client/PKI tests, make check with explicit envtest versions, and real Kafka/Kind checks for deletion and garbage collection where applicable. Record exact commands/results and unrun checks in linked PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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