Skip to content

Keep GitOps migration Jobs observable after completion #37

Description

@AntoineToussaint

Defect

The generated Kubernetes migration Job sets ttlSecondsAfterFinished: 0. In Argo CD, the Job is removed immediately after success, so the owning Application returns to OutOfSync/Missing and cannot provide durable Synced/Healthy evidence.

Acceptance criteria

  • Generated migration Jobs remain present after successful completion.
  • Argo CD can report the service Application as Synced/Healthy.
  • Template coverage prevents reintroducing immediate TTL cleanup.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions