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
Activity
[-]Filter by kind[/-][+]Exclude some resource kind[/+]sudermanjr commentedon Nov 17, 2022
The current setup allows you to override the list of deprecations that you are using if you would like to try that. I think adding that flag could be useful as well, but in the meantime check out - https://github.com/FairwindsOps/pluto/blob/master/docs/advanced.md#adding-custom-version-checks
niksauer commentedon Nov 21, 2022
That does not help since you cannot override anything contained in the default
versions.yamlthat Pluto uses 😔