The Secrets Provider image for Kubernetes is not updating the secrets file when the template in the ConfigMap is updated while using the push-to-file approach.
Steps to Reproduce
While deploying application make sure you are reading template from config map.
Once the application is deployed along with secrets provider image as sidecar, validate secrets file is generated and accessible by application container.
Now update the template in config map to add additional secret (you may use existing variable with different key in template file).
Wait for 1-2 mins to pick the template in shared volume mount to be updated.
Expected Results
The target secrets file must be updated as per template provided in config map.
Actual Results
The actual secrets file is not getting updated while template with in the shared volume is getting updated.
Reproducible
[X] Always
[ ] Sometimes
[ ] Non-Reproducible
Version/Tag number
What version of the product are you running? Any version info that you can
share is helpful. For example, you might give the version from Docker logs,
the Docker tag, a specific download URL, the output of the /info route, etc.
Summary
The Secrets Provider image for Kubernetes is not updating the secrets file when the template in the ConfigMap is updated while using the push-to-file approach.
Steps to Reproduce
Expected Results
The target secrets file must be updated as per template provided in config map.
Actual Results
The actual secrets file is not getting updated while template with in the shared volume is getting updated.
Reproducible
Version/Tag number
What version of the product are you running? Any version info that you can share is helpful. For example, you might give the version from Docker logs, the Docker tag, a specific download URL, the output of the
/inforoute, etc.Using the latest tag image.
Environment setup
Running in GKE cluster.
Additional Information
Add any other context about the problem here.