Skip to content

Detect *stale* tekton objects prior to a upgrade / reconciliaton #2474

@vdemeester

Description

@vdemeester

A set of stale tekton objects (PipelineRun, …) can block the entire upgrade process (see #2473). The operator should be able to detect if there is stale tekton objects and warn and pause the reconciliation until it gets resolved.

  • Stale object are object stuck in terminating state
    • Usually it means there is a deletionTimestamp (in metadata) and a finalizers … and it's old
  • To warn user, we should report something in the status.conditions stating that there is some stale objects, with some link or command to detect them.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/roadmapIssues that are part of the project (or organization) roadmap (usually an epic)kind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions