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
Copy file name to clipboardExpand all lines: docs/secret-management.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,7 @@ Any manual data change or deletion of the K8s Secret owned by a VaultSecret CR w
72
72
73
73
- `refreshPeriod`the pull interval for syncing Vault secrets with the K8s Secret. This settings takes precedence over any lease duration returned by vault, effectively controlling when exactly all vault secrets defined in the vaultSecretDefinitions should re-sync.
74
74
- `refreshThreshold`this is will instruct the operator to refresh the K8s Secret when a percentage of the lease duration has elapsed, if no `refreshPeriod` is specified. This is particularly useful for controlling when dynamic secrets should be refreshed before the lease duration is exceeded. The default is 90, meaning the secret would refresh after 90% of the time has passed from the vault secret's lease duration. When multiple vaultSecretDefinitions are defined, the smallest lease duration will be used when performing the scheduling for the next refresh.
75
+
- `syncOnResourceChange`if set to `true`, the operator will immediately resync the secret from Vault whenever the VaultSecret spec or metadata (labels/annotations) changes, bypassing the time-based refresh gate. By default this is `false`, meaning changes to the VaultSecret resource will only take effect at the next scheduled refresh (controlled by `refreshPeriod` or `refreshThreshold`). This is useful when you want spec changes like updating `output.stringData` templates or `vaultSecretDefinitions` to be reflected in the K8s Secret right away without waiting for the next refresh cycle.
75
76
- `vaultSecretDefinitions`is an array of Vault Secret References. Every `vaultSecretDefinition` has...
0 commit comments