Skip to content

Vault role for secret and configmap mutations #160

Description

@sagikazarmark

The default VAULT_ROLE env var sets a default for all kinds of mutations, regardless of where (namespace) the actual injection happens.

In case of pods, the injection happens in the pods's namespace. In case of secrets and configmaps, the injection happens in the vault secrets webhook namespace.

We should have a separate global default for these two cases.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/enhancementCategorizes issue or PR as related to an improvement.lifecycle/keepDenotes an issue or PR that should be preserved from going stale.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    🔖 Ready for work

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions