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
When consuming the path rabbitmq/creds/my-role from a SecretProviderClass, it works properly to generate the credentials on the fly. However, upon reaching the default rotation pool interval of 2 minutes configured in the Secrets Store CSI Driver, it will generate yet another credential.
You can see in the screenshot below that in 10~12 minutes it has generated 5 credentials. Because I have Reloader listening to the secrets, it also restarted the pod every 2 minutes.
It would be great if Vault CSI Driver would inspect the generated credentials for its validity before generating a new one.
The text was updated successfully, but these errors were encountered:
I have enabled and configured the RabbitMQ secrets engine to generate credentials for RabbitMQ as per this documentation: https://developer.hashicorp.com/vault/docs/secrets/rabbitmq
When consuming the path
rabbitmq/creds/my-role
from aSecretProviderClass
, it works properly to generate the credentials on the fly. However, upon reaching the default rotation pool interval of 2 minutes configured in the Secrets Store CSI Driver, it will generate yet another credential.You can see in the screenshot below that in 10~12 minutes it has generated 5 credentials. Because I have Reloader listening to the secrets, it also restarted the pod every 2 minutes.
It would be great if Vault CSI Driver would inspect the generated credentials for its validity before generating a new one.
The text was updated successfully, but these errors were encountered: