• 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

  • logLevelstring

    Deckhouse logging level.

    Default: "Info"

    Allowed values: Debug, Info, Error

  • nodeSelectorobject

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

    If the parameter is omitted or false, it 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

  • 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.

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

    Settings of the Deckhouse update mode and windows.

    • 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 CR ‘DeckhouseRelease’, which corresponds to the version by setting the `approved’ field to ‘true’.

      Default: "Auto"

      Allowed values: Auto, Manual

    • windowsarray of objects

      List of update windows.

      • daysarray of strings

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

        Allowed values of the array: Mon, Tue, Wed, Thu, Fri, Sat, Sun

      • fromstring

        Required value

        Start time of the update window (UTC timezone).

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

        Example:

        from: '13:00'
        
      • tostring

        Required value

        End time of the update window (UTC timezone).

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

        Example:

        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.