I am running several cronjobs on kubernetes cluster and want them to run on EDT timezone America/New_York. I would like to find out, how to ensure that my jobs run at specific EDT time. At present, all these jobs run with UTC timezone.
the POD images have been verified that they all have EDT timezone
can set manually timezone by going to each host machine/container
There was some suggestion on finding kubernetes controller and setting timezone on that particular host/container. I would appreciate,if someone can shed light on
a. How one can find kubernetes admin controller?
b. How one can set timezone automatically on the container via command-line or yaml file
I came across following git repo and it helped me solve the problem
https://github.com/hiddeco/cronjobber
Overall, it allows one to set timezone along with cron job specification.
Related
I'm trying to figure out how to show a timestamp for each line of STDOUT of an Argo Workflows pod. The init and wait containers by default show a timestamp, but never the main container.
The Argo CLI has a --timestamp flag when viewing logs.
Also the argo-java-client has a logOptionsTimestamps property that also enables timestamps.
However I cannot find a similar option when defining a Workflow in YAML. I've gone through the field reference guide but haven't been able to find something to enable timestamps in the main container.
Does anyone know if this is possible, or how to enable them?
Thanks,
Weldon
The reason init and wait log statements have timestamps is that the Argo executable's logger writes timestamps by default.
The --timestamps option does not cause the containers themselves to log timestamps. It just decorates each log line with a timestamp (kubectl has a similar option).
As far as I know, there's no way to declaratively cause code running in the main container to log timestamps. You'd have to modify the code itself to use a logger which inserts timestamps.
The task is to configure Cluster Autoscaler(CA) with 1 minute of scale-down time in DigitalOcean DOKS.
DOKS by default supports CA and having 10 mins of scale down time. Now i need to add below parameters as per my requirement.
Parameters need to modify to:
--scale-down-unneeded-time=10s
--scale-down-delay-after-add=30s
I tried in DO, but there is no place for adding/changing the parameters(or not sure if im missing anything).
Then tried in AWS EKS Cluste, Configured CA(no default support) with the above parameters, working fine.
Could anyone help me to configure these parameters in DOKS?
Found the root after the entier day.
It may be good for someone, so adding.
DigitalOcean K8S Cluster supports Cluster-AutoScaler(CA) by default. But not giviing explicit option to change its configurations.
We cannot change CA behaviour by passing parameters.
There is work in progress:
https://github.com/kubernetes/autoscaler/issues/3556
https://github.com/kubernetes/autoscaler/issues/3556#issuecomment-877015122
I am trying to change the sync period as mentioned in the following k8s document. I found the file named kube-controller-manager.yaml in /etc/kubernetes/manifests. I changed the timeoutSeconds: value from 15 secs(default) to 60 secs. Now I have 2 questions based on above info:
Is this the right way to change the sync period ? Cause I have read in the document that there is some flag named --horizontal-pod-autoscaler-sync-period, but adding that is also not working.
And any changes made to the file kube-controller-manager.yaml are getting restored to default whenever I restart the minikube? what should I do? Please let me know any solution or any view in this.
To change the sync period you have to run following command while starting the minikube.
minikube start --extra-config 'controller-manager.horizontal-pod-autoscaler-sync-period=10s'
We tried to harden the gke optimized image (gke-1.15.11) for our cluster. We took an ssh into the node instance and made the cis porposed changes in the /home/kubernetes/kubelet-config.yaml file and ran kubebench to check if all the conditions have passed around 8 condtions failed these where the exact conditions we changed in the file. But, then we made the exact argument changes in /etc/default/kubernetes and ran kubebench again the conditions passed. But, when we restarted the instance we all the changes we made in the /ect/default/kubernetes file where gone. Can someone let me know where we are going wrong or is there any other path where we have to make the cis benchmark suggested entries
GKE doesn't support user-provided node images as of April 2020. Recommended option is to create your own DaemonSet with host filesystem writes and/or host services restart to propagate all the required changes.
I have a Rundeck Rundeck 3.1.2-20190927 community, a Project with a scheduled job at 01:02:00 CET , and it works. BUT every night, I get a notification for this same job, scheduled at 00:00:00 CET ! I can't find any info in database or WebUI, can anybody help me ?
Thank you !
Nicolas
If you're using the same timezone configured in your Rundeck server, you don't need to specify it, remove the timezone of your job definition and your job runs using the Rundeck server timezone.