custom-cronjon-run - V 1
Automated Cronjob:
Our automation has created a secret-provider cronjob, acting as a sidecar, is responsible for interacting with the CyberArk service and retrieving secrets. This job runs every 24h to sync any CyberArk secret changes to your namespace. Once the secret has been synced to your namespace, your pods will need to be restarted to consume the new secrets.
If you have made changes to a secret and need it to be immediately consumed by your application, you will need to manually trigger the sync job and restart your deployment/statefulset. To run the Job immediately, you can run the command kubectl create job --from=cronjob/secrets-provider manual1 or perform the following steps in the Rancher UI:
Please allow up to 5 minutes for the sync job to finish. Once finished, you may manually restart your deployment for you application to consume the newly synced secrets (kubectl rollout restart deployment <deploymentname>).
If the Kubernetes secret is getting created for the 1st time, your deployment will fail to start and you will need to manually restart the deployment (kubectl rollout restart deployment <deploymentname>).
If your secret is not getting injected into your container, please contact L2 support at