cronjobber
cronjobber copied to clipboard
hiddeco
Cronjobber is a cronjob controller for Kubernetes with support for time zones
Hello, I have a two CronJob the one set to `0 1 * * *` in `Europe/Paris` which is running at 3 CEST, the other one scheduled at `0 3...
This has the advantage that you can set longer tzcronjob names and they will then automatically be shortend by kubernetes when creating a job.
According to the documentation of both the cronjob and tzcronjob the defaults for the job limits are either 1 for failed jobs and 3 for successful jobs. Currently tzCronjobber ignores...
Nice job, thanks for releasing this! Before starting to use this, I would like to know a little more about the behavior of cronjobber during edge cases: - what happens...
CronJobber is deployed on `cronjobber` NS and other regular `CronJob`s are deployed on NS `zzzzz` To test my `TZCronJob` was deployed with `schedule: */1 20 * * *` @ 20.02...
> Deprecated in v1.16, planned for removal in v1.22. Use apiextensions.k8s.io/v1 CustomResourceDefinition instead. CRDs v1 allows the TZCronJob to be registered as part of the K8s API and be detected...
As an admin I can easily deploy the examples you provide. As another user (e.g. ci user) I get the following error: tzcronjobs.cronjobber.hidde.co "my-dummy-service" is forbidden: User "ci-user" cannot get...
I cannot find a Helm chart version of it at https://hub.helm.sh Do you have plans to create one or should everyone do it on their own manually?
First of all thanks for this awesome component. While official Kubernetes is expecting to add a Timezone soon but it is getting delayed a lot and we are using CronJobber...
Do you apply the same concurrent policy of k8scronjob? Even if I apply 'forbid' and 'replace', it seems to be set to 'allow'.
