Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
kszicsillag opened this issue Feb 20, 2025 · 0 comments
Open

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

kszicsillag opened this issue Feb 20, 2025 · 0 comments
Labels
question Further information is requested

Comments

@kszicsillag
Copy link

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.

@kszicsillag kszicsillag added the question Further information is requested label Feb 20, 2025
@kszicsillag kszicsillag changed the title [Question]Honring nbf (activation date) of Key Vault secrets [Question]Honoring nbf (activation date) of Key Vault secrets Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant