Closed ejschoen closed 4 days ago
I think this is an interesting feature request, To avoid having multiple secrets, it woul be interesting to update an existing k8s secret object by appending a non existant key.
This issue is stale because it has been open 14 days with no activity. Please comment or this will be closed in 7 days.
This issue was closed because it has been stalled for 21 days with no activity. Feel free to re-open if you are experiencing the issue again.
If secretObjects.secretName refers to a pre-existing secret, a pod configuration error is flagged because the secret is missing the key requested in the pod's env.<>.valueFrom.secretRef.key field. If the secret exists and the requested key exists, there is no error, but the vault value is not synced to the secret value.
It might help if the documentation for syncing to Kubernetes secrets explicitly states that the SPC must create the secret.