How do I find out all Deckhouse parameters?

All the essential Deskhouse settings (including module parameters) are stored in the deckhouse ConfigMap in the d8-system namespace. You can view its contents using the command below:

kubectl -n d8-system get cm deckhouse -o yaml

How do I find the documentation for the version installed?

The documentation for the Deckhouse version running in the cluster is available at deckhouse.<cluster_domain>, where <cluster_domain> is the DNS name that matches the template defined in the global.modules.publicDomainTemplate parameter.

How do I set the desired release channel?

Change (set) the module’s releaseChannel parameter to automatically switch to another release channel (and minimize version drift in the cluster). It will activate the mechanism of automatic stabilization of the release channel.

Here is an example of the module configuration:

deckhouse: |
  releaseChannel: RockSolid

How does the mechanism of automatic stabilization of the release channel work?

Deckhouse will switch to the image with the corresponding Docker image tag in response to setting the releaseChannel parameter. No other action is required on the part of the user.

Note: Switching is not instantaneous and relies on the Deckhouse update process.

The release channel stabilization script runs every 10 minutes. It implements the following algorithm:

  • If the specified release channel matches the Deckhouse Docker image’s tag — do nothing;

  • When switching to a more stable release channel (e.g., Alpha -> EarlyAccess), the gradual transition takes place:

    • First, the script compares the digests of Docker image tags that correspond to the current release channel and the next more stable channel (Alpha and Beta in our example).

    • If the digests are equal, the script checks the next tag (in our example, this tag corresponds to the EarlyAccess release channel).

    • As a result, Deckhouse will switch to a more stable release channel with a digest equal to the current one.

  • Suppose a less stable release channel is specified than the channel that corresponds to the current tag of the Deckhouse Docker image. In that case, the script compares digests corresponding to the Docker images for the current release channel and the next, less stable one. For example, if you need to switch to the Alpha channel from the EarlyAccess channel, the script will compare the EarlyAccess and Beta channels:

    • If digests are not equal, Deckhouse switch to the next release channel (Beta in our case). Such an approach ensures that some crucial migrations are performed during Deckhouse upgrades.

    • If the digests are equal, the script checks the next less stable release channel (Alpha in our case).

    • When the script reaches the desired release channel (Alpha in our example), Deckhouse will switch to it regardless of the results of the digest comparison.

Since the stabilization script runs continuously, Deckhouse will eventually end up in a state where the tag of its Docker image corresponds to the release channel set.

How do I run Deckhouse on a particular node?

Set the nodeSelector parameter of the deckhouse module and don’t set tolerations. The necessary values for the tolerations parameter will be set automatically.

You should also avoid using CloudEphemeral nodes. Otherwise, a situation may occur when the target node is not in the cluster and node ordering for some reason is impossible.

Here is an example of the module configuration:

deckhouse: |
  nodeSelector:
    node-role.deckhouse.io/deckhouse: ""