Skip to content

Ability to specify exemptions #215

@gabegorelick

Description

@gabegorelick

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementAdding additional functionality or improvementspinnedPrevents stalebot from removingpriority: couldFuture work depending on bandwidth and availability

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions