Skip to content
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

How do I change the rancher-server timezone settings? #18913

Closed
portfield-slash opened this issue Mar 14, 2019 · 8 comments
Closed

How do I change the rancher-server timezone settings? #18913

portfield-slash opened this issue Mar 14, 2019 · 8 comments
Labels
kind/question Issues that just require an answer. No code change needd status/stale

Comments

@portfield-slash
Copy link

portfield-slash commented Mar 14, 2019

What kind of request is this (question/bug/enhancement/feature request):
question

Steps to reproduce (least amount of steps as possible):
I want to use kubernetes cronjob. My timezone setting is UTC+9.
I believe that it is necessary to change the timezone setting of the rancher-server container.
Is there any other good way?

Result:

Other details that may be helpful:

Environment information

  • Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
    v2.1.7

  • Installation option (single install/HA):
    single install

Cluster information

  • Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
  • Machine type (cloud/VM/metal) and specifications (CPU/memory):
  • Kubernetes version (use kubectl version):
- Cluster type (Hosted/Infrastructure Provider/Custom/Imported):Custom
- Machine type (cloud/VM/metal) and specifications (CPU/memory):cloud
- Kubernetes version (use `kubectl version`):v1.13.4
  • Docker version (use docker version):
Client:
 Version:         1.13.1
 API version:     1.26
 Package version: docker-1.13.1-88.git07f3374.el7.centos.x86_64
 Go version:      go1.9.4
 Git commit:      07f3374/1.13.1
 Built:           Fri Dec  7 16:13:51 2018
 OS/Arch:         linux/amd64

Server:
 Version:         1.13.1
 API version:     1.26 (minimum version 1.12)
 Package version: docker-1.13.1-88.git07f3374.el7.centos.x86_64
 Go version:      go1.9.4
 Git commit:      07f3374/1.13.1
 Built:           Fri Dec  7 16:13:51 2018
 OS/Arch:         linux/amd64
 Experimental:    false
@cjellick cjellick added kind/question Issues that just require an answer. No code change needd version/2.0 labels Mar 16, 2019
@cjellick
Copy link

Change the timezone of the underlying host?

@portfield-slash
Copy link
Author

@cjellick
Thank you for your comment.

I want to do it.
I changed the OS settings of the rancher-server container.
It confirmed that the OS settings were changed with the date command.

I then scheduled a cronjob, but Rancher's time settings didn't change.

@bou7mis
Copy link

bou7mis commented May 1, 2019

+1. I have a scheduled job on my production cluster that is programmed like so : "0 6,12,18 * * *". Timezone is correctly set in the host node and i confirmed that with date command. But i noticed from workload logs that the job is executing at 8am, 2pm and 8pm everyday. Is there a timezone setting somewhere to configure in rancher cluster settings ?

@wisepotato
Copy link

also having this problem, because rancher is using UTC, anda ll docker containers that execute from it are UTC, but my server host is CEST

@dunxiii
Copy link

dunxiii commented Sep 7, 2019

I also see this problem, host has the correct timezone set but rancher is off by 2 hours.

@portfield-slash
Copy link
Author

Duplicate of #19675 #22259

@pakali
Copy link

pakali commented Apr 10, 2020

Edit cluster.yaml (Edit cluster > Edit as YAML) and add this lines to services section:

services:
    kube-controller:
      extra_binds:
        - '/etc/localtime:/etc/localtime'

After that configure correct timezone on Control Plane role nodes.

@stale
Copy link

stale bot commented Jul 11, 2021

This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.

@stale stale bot added the status/stale label Jul 11, 2021
@stale stale bot closed this as completed Jul 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Issues that just require an answer. No code change needd status/stale
Projects
None yet
Development

No branches or pull requests

7 participants