Skip to content

[Question]Honoring nbf (activation date) of Key Vault secrets #815

@kszicsillag

Description

@kszicsillag

Note: Make sure to check out known issues (https://github.com/sparebankenvest/azure-key-vault-to-kubernetes#known-issues) before submitting

How can one make sure that no Key Vault secret gets injected that is not yet active (i.e. its nbf field refers to a future date)

Your question
A clear and concise question.

To Reproduce
If question relates to a certain behavior, describe steps to reproduce:

Logs
If applicable, add logs to help add context to your question.

Additional context
Add any other context about the question here.

The Key Vault doc states this about the nbf field of secrets.

nbf: IntDate, optional, default is now. The nbf (not before) attribute identifies the time before which the secret data SHOULD NOT be retrieved, except in particular situations. This field is for informational purposes only. Its value MUST be a number containing an IntDate value.

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions