Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for Managed Service for Kubernetes
    • Resolving the `Timed out waiting for the condition` error when mounting a PVC
    • Resolving the `Timed out waiting for the condition` error when mounting a volume with a large number of files
    • Hosts of the Managed Service for Kubernetes node groups stay in the `RECONCILING` status for a long time
    • Cyclical restarts of the `kube-dns-autoscaler` pod
    • Cannot reduce the number of nodes in a Managed Service for Kubernetes group
    • Cannot increase the number of nodes in a Managed Service for Kubernetes group
    • Resolving the `Multi-Attach error for volume` error
    • Resolving the `DEADLINE_EXCEEDED` error
    • Troubleshooting time synchronization issues on Managed Service for Kubernetes cluster nodes
    • Troubleshooting DNS name resolving issues in Managed Service for Kubernetes
    • Resolving the `0/10 nodes are available - node(s) had untolerated taint` error
    • The cluster remains in the `STARTING` status for too long
    • Cluster pods remain in the `PENDING` status for too long
    • Troubleshooting HPA issues in Managed Service for Kubernetes
    • Resolving the `Can't use allocation_policy.locations.subnet_id together with node_template.network_interface_specs` error
    • Troubleshooting issues when mounting volumes to Managed Service for Kubernetes cluster pods using Container Storage Interface for S3
    • Managed Service for Kubernetes cluster remains `STARTING` for too long after renaming
    • How to add and update Linux SSH keys on Managed Service for Kubernetes node group hosts
    • How to assign static external IP addresses to Managed Service for Kubernetes cluster nodes
    • How to provide Kubernetes nodes with internet access
    • How to create an internal Ingress controller
    • How to set up autodeletion of old images from Managed Service for Kubernetes nodes
    • How to find out the external IP address of a Managed Service for Kubernetes node
    • How to use Certificate Manager certificates in load balancers or in Managed Service for Kubernetes
    • How to change the time zone on Managed Service for Kubernetes cluster nodes
    • How to find out the ephemeral storage size for a Managed Service for Kubernetes node

In this article:

  • Case description
  • Solution
  • If nothing helped
  1. Managed Service for Kubernetes
  2. How to change the time zone on Managed Service for Kubernetes cluster nodes

How to change the time zone on Managed Service for Kubernetes cluster nodes

Written by
Yandex Cloud
Updated at December 17, 2025
  • Case description
  • Solution
  • If nothing helped

Case descriptionCase description

  • You need to change the default time zone on Managed Service for Kubernetes cluster nodes.
  • You need to set the time zone for one or more Managed Service for Kubernetes cluster nodes.

SolutionSolution

All VMs created in Yandex Cloud, including Managed Service for Kubernetes cluster nodes, synchronize their system clock with the physical hypervisor in the UTC+0 time zone.

Tip

We recommend updating your app code to change the time zone to the one you need, e.g., UTC+3 (Moscow/Riyadh).

Setting the time zone can also be important when running CronJob events, as such events in Managed Service for Kubernetes default to the time specified on the Controller Manager. For step-by-step guide on specifying the time zone for specific CronJob events, refer to this Kubernetes article.

If nothing helpedIf nothing helped

If the above actions did not help, create a support ticket. Provide the following information in your ticket:

  1. Managed Service for Kubernetes cluster ID.
  2. Your use case that involves changing the default time zone to the one of your choice.

Was the article helpful?

Previous
How to use Certificate Manager certificates in load balancers or in Managed Service for Kubernetes
Next
How to find out the ephemeral storage size for a Managed Service for Kubernetes node
© 2025 Direct Cursus Technology L.L.C.