Similar to https://polaris.docs.fairwinds.com/customization/exemptions.
Example use case: policy/v1beta1 was deprecated in Kubernetes 1.21, but won't be removed until 1.25. For my own first-party code, I want to enforce that policy/v1 is used for any new code. But it doesn't make sense for third party vendors to migrate to policy/v1 yet since that would mean dropping support for Kubernetes < 1.21 (1.20 isn't EOL until 2022-02-28, for example). Thus, I need to be able to add exemptions for certain resources to allow them to use deprecated APIs without breaking CI checks.
As a workaround, I'm using --only-show-removed to only flag usages of APIs that definitely won't work in the current target version. But this means that nothing stops you from adding new consumers of deprecated APIs.
Similar to https://polaris.docs.fairwinds.com/customization/exemptions.
Example use case:
policy/v1beta1was deprecated in Kubernetes 1.21, but won't be removed until 1.25. For my own first-party code, I want to enforce thatpolicy/v1is used for any new code. But it doesn't make sense for third party vendors to migrate topolicy/v1yet since that would mean dropping support for Kubernetes < 1.21 (1.20 isn't EOL until 2022-02-28, for example). Thus, I need to be able to add exemptions for certain resources to allow them to use deprecated APIs without breaking CI checks.As a workaround, I'm using
--only-show-removedto only flag usages of APIs that definitely won't work in the current target version. But this means that nothing stops you from adding new consumers of deprecated APIs.