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

How to explicitly enable the module…

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

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

Use the monitoringKubernetes 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 monitoring-kubernetes module:

apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: monitoring-kubernetes
spec:
  enabled: true

Example of disabling the monitoring-kubernetes module:

apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: monitoring-kubernetes
spec:
  enabled: false

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

Example of the ModuleConfig/monitoring-kubernetes resource for configuring the module:

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

Parameters

Schema version: 1

  • highAvailabilityboolean

    Manually enable the high availability mode.

    By default, Deckhouse automatically decides whether to enable the HA mode. Click here to learn more about the HA mode for modules.

    Examples:

    highAvailability: true

    highAvailability: false
  • nodeSelectorobject

    The same as in the pods’ spec.nodeSelector parameter in Kubernetes.

    If the parameter is omitted or false, it will be determined automatically.

    Example:

    nodeSelector:
  disktype: ssd
  • tolerationsarray of objects

    The same as in the pods’ spec.tolerations parameter in Kubernetes;

    If the parameter is omitted or false, it will be determined automatically.

    Example:

    tolerations:
- key: key1
  operator: Equal
  value: value1
  effect: NoSchedule
    • tolerations.effectstring
    • tolerations.keystring
    • tolerations.operatorstring
    • tolerations.tolerationSecondsinteger
    • tolerations.valuestring
  • vpaobject

    VPA settings for kube-state-metrics deployment.

    Example:

    vpa:
  kubeStateMetricsMaxCPU: 130m
  kubeStateMetricsMaxMemory: 115Mi
    • vpa.kubeStateMetricsMaxCPU

      CPU requests.

      Examples:

      kubeStateMetricsMaxCPU: 3

      kubeStateMetricsMaxCPU: 1000m
    • vpa.kubeStateMetricsMaxMemory

      Memory requests.

      Example:

      kubeStateMetricsMaxMemory: 3Mi