-
Notifications
You must be signed in to change notification settings - Fork 459
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Official documentation on using Reloader with a Cron Job ? #543
Comments
Why did you close #542? |
Closed the other issue as Duplicate Issues were created. Asking this question , tried using reloader by using version 1.0.42 in a k3s cluster.
I have a configMap in the same namespace ' abc' if i were to change a key: value , the cron job would be triggered. The cron job has been annotated with
my-config being the configmap in namespace abc. Service account has been created " |
i stopped getting the log ensuring namespace selector was pointing to abc namespace, hence it was able to find -myconfig , but my cron job does have an annotations with
Expected Behaviour Seen behaviour -> no logs seen in reloader pods mentioning change in "abc" config map. Cron job not triggered.
|
I feel the cluster Role and the Role binding needs to be updated for a batch/job for the service account that is created with it |
Would be good if document is updated with CronJob support. I tried adding annotation for job like below
But seems not working. Im using latest Helm chart version 1.0.44 |
This was fixed in 1.0.45 and releases above |
Documentation is still missing |
Just noting that the HelmChart does not add the RBAC permissions to patch or update a Job/CronJob. It doesn't look like the controller (v1.0.52) is looking for and Jobs to update either. I would like to see this update a Job when a secret changes (and hopefully the Job will start again).
|
I have been following Reloader for the PR : #486
Issue : Reloader Issue Support for Cron Job
Is there a readme that's available ? for this change , would be really helpful
The text was updated successfully, but these errors were encountered: