The module has 46 alerts.

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…

Set the spec.enabled module parameter to true or false in the ModuleConfig/monitoring-kubernetes resource (create it, if necessary) to explicitly enable or disable the module, or use the deckhouse-controller module command in the d8-system/deckhouse pod.

Example of enabling the module:

  • by using the ModuleConfig resource:

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

  • by using the deckhouse-controller command (you need a kubectl, configured to work with the cluster):

    kubectl -ti -n d8-system exec svc/deckhouse-leader -c deckhouse -- deckhouse-controller module enable monitoring-kubernetes

Example of disabling the module:

  • by using the ModuleConfig resource:

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

  • by using the deckhouse-controller command (you need a kubectl, configured to work with the cluster):

    kubectl -ti -n d8-system exec svc/deckhouse-leader -c deckhouse -- deckhouse-controller module disable monitoring-kubernetes

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

  • settings
    object
    • settings.ebpfExporterEnabled
      boolean

      Set to ‘false’ to disable ebpf_exporter in case it behaves incorrectly.

      Default: true

      Example:

      ebpfExporterEnabled: false
    • settings.highAvailability
      boolean

      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
    • settings.nodeSelector
      object

      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
    • settings.tolerations
      array 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
      • settings.tolerations.effect
        string
      • settings.tolerations.key
        string
      • settings.tolerations.operator
        string
      • settings.tolerations.tolerationSeconds
        integer
      • settings.tolerations.value
        string
    • settings.vpa
      object

      VPA settings for kube-state-metrics pods.

      Example:

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

        The maximum value that the VPA can set for the CPU requests.

        Examples:

        kubeStateMetricsMaxCPU: 3

        kubeStateMetricsMaxCPU: 1000m
      • settings.vpa.kubeStateMetricsMaxMemory

        The maximum memory requests the VPA can set.

        Example:

        kubeStateMetricsMaxMemory: 3Mi