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
Is your feature request related to a problem? Please describe.
We would like exclude certain resources from the deprecation warnings output (e.g. PodDisruptionBudget that will be removed in 1.25), simply because the upgrade of those resources depend on another team, and we would still like to integrate Pluto in our CI, without having it be red until those are fixed.
This way, people would be able to have a green pipeline with Pluto at all times, while gradually migrating their deprecated resources.
Describe the solution you'd like pluto detect-helm --excludeKind=PodDisruptionBudget -o wide
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We would like exclude certain resources from the deprecation warnings output (e.g.
PodDisruptionBudget
that will be removed in 1.25), simply because the upgrade of those resources depend on another team, and we would still like to integrate Pluto in our CI, without having it be red until those are fixed.This way, people would be able to have a green pipeline with Pluto at all times, while gradually migrating their deprecated resources.
Describe the solution you'd like
pluto detect-helm --excludeKind=PodDisruptionBudget -o wide
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: