You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the Rollout match selector to AnalysisRuns as labels
Use Cases
At the moment there is no easy to select all of the AnalysisRuns that belong to a specific rollout so if you want to review the past history with kubectl it's painful to select them. While the AnalysisRun does have the ownerReference set to the Rollout this is not selectable with a field-selector or any other mechanism AFAIK, typically some scripting would be needed to do so.
The idea here is to basically do the same thing with AnalysisRuns that already happens with ReplicaSets and Pods.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered:
Summary
Add the Rollout match selector to AnalysisRuns as labels
Use Cases
At the moment there is no easy to select all of the AnalysisRuns that belong to a specific rollout so if you want to review the past history with kubectl it's painful to select them. While the AnalysisRun does have the ownerReference set to the Rollout this is not selectable with a field-selector or any other mechanism AFAIK, typically some scripting would be needed to do so.
The idea here is to basically do the same thing with AnalysisRuns that already happens with ReplicaSets and Pods.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: