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…

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

Example of enabling the node-manager module:

apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: node-manager
spec:
  enabled: true

Example of disabling the node-manager module:

apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: node-manager
spec:
  enabled: false

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

Example of the ModuleConfig/node-manager resource for configuring the module:

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

Parameters

Schema version: 1

  • allowedBundlesarray of strings

    Names of available bashible OS bundles to reduce Helm release size.

    Default: ["ubuntu-lts","centos","debian","redos","alteros","astra"]

    Example:

    allowedBundles:
- ubuntu-lts
    • Element of the arraystring

      Allowed values: ubuntu-lts, centos, debian, redos, alteros, astra

  • allowedKubernetesVersionsarray of strings

    Names of available Kubernetes versions to reduce Helm release size.

    Default: ["1.21","1.22","1.23","1.24","1.25"]

    Example:

    allowedKubernetesVersions:
- '1.21'
- '1.23'
  • earlyOomEnabledboolean

    Set to ‘false’ to disable early OOM killer in case it behaves incorrectly.

    Default: true

    Example:

    earlyOomEnabled: false
  • instancePrefixstring

    The prefix to use when creating instances via the corresponding cloud provider module.

    The default value can be calculated based on the ClusterConfiguration struct if the cluster is installed via the Deckhouse installer.

    Example:

    instancePrefix: kube
  • mcmEmergencyBrakeboolean

    Set to ‘true’ to disable machine-controller-manager in case of potentially cluster-damaging changes.

    Warning! Use this flag only if you know what you are doing and clearly understand the consequences.

    Default: false

    Example:

    mcmEmergencyBrake: false