You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.The text was updated successfully, but these errors were encountered: