Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
vdemeester opened this issue Dec 20, 2024 · 0 comments
Open

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

vdemeester opened this issue Dec 20, 2024 · 0 comments
Labels
area/roadmap Issues that are part of the project (or organization) roadmap (usually an epic) kind/feature Categorizes issue or PR as related to a new feature.

Comments

@vdemeester
Copy link
Member

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.
@vdemeester vdemeester added kind/feature Categorizes issue or PR as related to a new feature. area/roadmap Issues that are part of the project (or organization) roadmap (usually an epic) labels Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/roadmap Issues that are part of the project (or organization) roadmap (usually an epic) kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vdemeester