Configure NTP server for a regional cluster¶

If you did not add the NTP server parameters during the management cluster bootstrap, configure them on the existing regional cluster as required. These parameters are applied to all machines of regional and managed clusters in the specified region.

Caution

The procedure below applies only if ntpEnabled=true (default) was set during a management or regional cluster bootstrap. Enabling or disabling NTP after bootstrap is not supported.

Warning

The procedure below triggers an upgrade of all clusters in a specific region, which may lead to workload disruption during nodes cordoning and draining.

To configure an NTP server for a regional cluster:

Download your management cluster kubeconfig:
1. Log in to the Container Cloud web UI with the m:kaas:namespace@operator or m:kaas:namespace@writer permissions.
2. Switch to the required project using the Switch Project action icon located on top of the main left-side navigation panel.
3. Expand the menu of the tab with your user name.
4. Click Download kubeconfig to download kubeconfig of your management cluster.
5. Log in to any local machine with kubectl installed.
6. Copy the downloaded kubeconfig to this machine.
Use the downloaded kubeconfig to edit the management cluster:
```
kubectl --kubeconfig <kubeconfigPath> edit -n <projectName> cluster <managementClusterName>
```
In the command above and the step below, replace the parameters enclosed in angle brackets with the corresponding values of your cluster.

In the regional section, add the ntp:servers section with the list of required server names:

spec:
  ...
  providerSpec:
    value:
      kaas:
      ...
      ntpEnabled: true
      ...
        regional:
          - helmReleases:
            - name: <providerName>
              values:
                config:
                  lcm:
                    ...
                    ntp:
                      servers:
                      - 0.pool.ntp.org
                      ...