Update Synced kubernetes native secret as well after a pod restart

[navapias]

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:

• Secrets Store CSI Driver version: 1.4.4
• Kubernetes version: 1.27

[srreddy2020]

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.

Do we have any solution for this.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten