• bundlestring

    The Deckhouse bundle defines a set of modules enabled by default.

    • Default — the recommended set of modules for cluster operation: monitoring, authorization control, networking and other needs (the current list is available here).
    • Minimal — the minimum possible bundle option (includes a single module — this one).
    • Managed — the bundle aimed at clusters managed by cloud providers (e.g., Google Kubernetes Engine).

    Default: "Default"

    Allowed values: Default, Minimal, Managed


    bundle: Default
  • logLevelstring

    Deckhouse logging level.

    Default: "Info"

    Allowed values: Debug, Info, Error


    logLevel: Info
  • nodeSelectorobject

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

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

  • releaseChannelstring

    Desirable Deckhouse release channel (Deckhouse will switch to it when such an opportunity appears).

    The order in which the stability of the release channel increases (from less stable to more stable): Alpha, Beta, EarlyAccess, Stable, RockSolid.

    Allowed values: Alpha, Beta, EarlyAccess, Stable, RockSolid


    releaseChannel: Stable
  • tolerationsarray of objects

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

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

    • effectstring
    • keystring
    • operatorstring
    • tolerationSecondsinteger
    • valuestring
  • updateobject

    Settings of the Deckhouse update mode and windows.


      - from: '8:00'
        to: '15:00'
        - Tue
        - Sat
      disruptionApprovalMode: Manual
        webhook: https://release-webhook.mydomain.com
        minimalNotificationTime: 6h
    • disruptionApprovalModestring

      Deckhouse release update disruption mode:

      • Auto — approves release with disruptions (potentially dangerous changes) automatically.
      • Manual — requires manual release confirmation (set annotation release.deckhouse.io/disruption-approved=true).

      Default: "Auto"

      Allowed values: Auto, Manual

    • modestring

      Deckhouse minor version update mode (release change). Does not affect patch version updates.

      • Auto — all updates are applied automatically.

        Deckhouse minor version updates (release updates, for example, from v1.26.* to v1.27.*), are applied according to the update windows or (if no update windows are set) as they appear on the corresponding release channel;

      • Manual — to change a minor version of Deckhouse (for example, from v1.26.* to v1.27.*), manual confirmation is required.

        To confirm the update, edit custom resource ‘DeckhouseRelease’, which corresponds to the version by setting the `approved’ field to ‘true’.

      Default: "Auto"

      Allowed values: Auto, Manual

    • notificationobject

      Settings for sending notifications of scheduled Deckhouse updates.

      Notifications are sent only when the automatic update mode is set.

      Alerts are sent only for Deckhouse minor version changes — no alerts are sent for patch version changes.


        webhook: https://release-webhook.mydomain.com
        minimalNotificationTime: 8h
      • minimalNotificationTimestring

        The minimum time that must pass from the notification before the update.

        The update mechanism ensures that Deckhouse will not be updated before the specified time.

        When using update windows, the Deckhouse update after the notification will happen at the nearest possible update window, but not before the time specified in minimalNotificationTime expires.

        Pattern: ^[0-9]+[mh]{1}$


        minimalNotificationTime: 6h
      • tlsSkipVerifyboolean

        Skip TLS certificate verification while webhook request.

        Default: false

      • webhookstring

        URL for an external webhook handler.

        The POST request will be sent on the webhook URL after a new minor version of Deckhouse appears on the update channel before it is applied to the cluster.

        Use the minimalNotificationTime parameter if necessary to set the minimum time that must elapse before updating from the moment of notification.

        Example of the POST request payload (Content-Type: application/json):

          "version": "1.36",
          "requirements":  {"k8s": "1.20.0"},
          "changelogLink": "https://github.com/deckhouse/deckhouse/changelog/1.36.md",
          "applyTime": "2023-01-01T14:30:00Z00:00",
          "message": "New Deckhouse Release 1.36 is available. Release will be applied at: Friday, 01-Jan-22 14:30:00 UTC"

        Description of POST request fields:

        • version - string, minor version number;
        • requirements - object, version requirements;
        • changelogLink - string, a URL to the minor version changelog;
        • applyTime - string, date and time of the scheduled update (taking into account the configured update windows) in RFC3339 format;
        • message - string, a text message about the availability of the new minor version and the scheduled update time.

        Pattern: ^https?://[^\s/$.?#].[^\s]*$


        webhook: https://webhook.site/#!/bc8f71ac-c182-4181-9159-6ba6950afffa
    • windowsarray of objects

      List of update windows during the day.

      • daysarray of strings

        The days of the week on which the update window is applied.


        - Mon
        - Wed
        • Element of the arraystring

          Day of the week.

          Allowed values: Mon, Tue, Wed, Thu, Fri, Sat, Sun


      • fromstring

        Required value

        Start time of the update window (UTC timezone).

        Should be less than the end time of the update window.

        Pattern: ^(?:\d|[01]\d|2[0-3]):[0-5]\d$


        from: '13:00'
      • tostring

        Required value

        End time of the update window (UTC timezone).

        Should be more than the start time of the update window.

        Pattern: ^(?:\d|[01]\d|2[0-3]):[0-5]\d$


        to: '18:30'

Note (!) that Deckhouse will stop working if there is a nonexistent label in nodeSelector or tolerations specified are incorrect. You need to change the values to the correct ones in configmap/deckhouse and deployment/deckhouse to get Deckhouse back on track.