VSS: Add requeue configuration flags #927
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When operating the vault-secrets-operator for multiple development teams, it would be great to have some more detailed control over the refresh interval of VaultStaticSecrets and the possible load that could be caused on the Vault server. Therefore, I would like to add the following parameters:
--min-refresh-after-vss- To prevent users from trying to update secrets every second and causing a high load on the Vault server.--default-refresh-after-vss- To provide a cluster-wide default value for the refresh interval of VaultStaticSecrets for more convenience.--hmac-horizon-vss- To use some larger interval before the next drift detection happens in case most VaultStaticSecrets rely on instant updates.