The module is enabled by default in the Default bundle. The module is disabled by default in the following bundles: Managed, Minimal.

How to explicitly enable the module…

Note that the configOverrides parameter of the InitConfiguration resource is used when installing Deckhouse, not ModuleConfig.

Set the chronyEnabled: true or chronyEnabled: false in the configOverrides parameter to explicitly enable or disable the module when installing Deckhouse.

Use the chrony section of the configOverrides parameter to configure the module when installing Deckhouse.

Set the spec.enabled module parameter to true or false to explicitly enable or disable the module.

Example of enabling the chrony module:

apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: chrony
spec:
  enabled: true

Example of disabling the chrony module:

apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: chrony
spec:
  enabled: false

The module is configured using the ModuleConfig custom resource named chrony (learn more about setting up Deckhouse…).

Example of the ModuleConfig/chrony resource for configuring the module:

apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: chrony
spec:
  version: 1
  enabled: true
  settings: # <-- Module parameters from the "Parameters" section below.

Parameters

Schema version: 1

  • ntpServersarray of strings

    NTP servers to sync.

    Default: ["pool.ntp.org"]

    Examples:

    ntpServers:
- pool.ntp.org

    ntpServers:
- pool.ntp.org
- ntp.ubuntu.com

An example of the configuration

apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: chrony
spec:
  settings:
    ntpServers:
      - pool.ntp.org
      - ntp.ubuntu.com
  version: 1