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
Describe the solution you'd like
Currently when a pod is restarted the secret value in the volume mounts inside the pod get updated, but the synced native secret does not get updated. The code shows only a create a option for the native secret and there is no update. Each time the synced native secret needs to be updated, it needs to be deleted before the pod restart. A solution is required to update the synced secret as well after the pod restart.
I also Observed the same behavior.
When Secrets are updated at Aws Secrets manger, if we restart the deployment Secrets are not updating in k8s secret.
we need to delete k8s secret first then if we restart the deployment, its creating the new secret with new secret from Aws secrets manger.
Describe the solution you'd like
Currently when a pod is restarted the secret value in the volume mounts inside the pod get updated, but the synced native secret does not get updated. The code shows only a create a option for the native secret and there is no update. Each time the synced native secret needs to be updated, it needs to be deleted before the pod restart. A solution is required to update the synced secret as well after the pod restart.
Anything else you would like to add:
There is no else condition here,
https://github.com/kubernetes-sigs/secrets-store-csi-driver/blob/main/controllers/secretproviderclasspodstatus_controller.go#L312
Is this an intended behavior since the controller will not be able to find out accurately as to who/which system created this secret if it already exists?
Environment:
The text was updated successfully, but these errors were encountered: