Available with limitations in:  CSE Lite (1.73), CSE Pro (1.73)

Available without limitations in:  EE

How to explicitly enable the module…

You may explicitly enable or disable the module in one of the following ways:

  • Via Deckhouse web UI. In the “System” → “System Management” → “Deckhouse” → “Modules” section, open the operator-argo module and enable (or disable) the “Module enabled” toggle. Save changes.

    Example:

    Module enable/disable interface

  • Via Deckhouse CLI (d8).

    Use the d8 system module enable command for enabling, or d8 system module disable command for disabling the module (you need Deckhouse CLI (d8), configured to work with the cluster).

    Example of enabling the module:

    d8 system module enable operator-argo

  • Using ModuleConfig operator-argo.

    Set spec.enabled to true or false in ModuleConfig operator-argo (create it if necessary);

    Example of a manifest to enable module operator-argo:

    apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: operator-argo
spec:
  enabled: true

How to configure the module…

You can configure the module in one of the following ways:

  • Via Deckhouse web UI.

    In the “System” → “System Management” → “Deckhouse” → “Modules” section, open the operator-argo module and enable the “Advanced Settings” switch. Fill in the required fields in the “Configuration” tab or specify the module settings in YAML format on the “YAML” tab, excluding the settings section. Save the changes.

    Example:

    Module Setup Interface

    You can also edit the ModuleConfig object operator-argo on the “YAML” tab in the module settings window (“System” → “System Management” → “Deckhouse” → “Modules”, open the module operator-argo) by specifying the schema version in the spec.version parameter and the necessary module parameters in the spec.settings section.

  • Via Deckhouse CLI (d8) (requires Deckhouse CLI (d8) configured to work with the cluster).

    Edit the existing ModuleConfig operator-argo (for more details on configuring Deckhouse, see the documentation) by executing the following command:

    d8 k edit mc operator-argo

    Make the necessary changes in the spec.settings section. If necessary, specify the schema version in the spec.version parameter. Save the changes.

    You can also create a file with manifest for ModuleConfig operator-argo using the example below. Fill in the spec.settings section with the required module parameters. If necessary, specify the schema version in the spec.version parameter.

    Apply the manifest using the following command (indicate the manifest file name):

    d8 k apply -f <FILENAME>

    Example of a manifest for ModuleConfig operator-argo:

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

How to change the module release channel…

To change the module release channel, follow the instruction.

Parameters

Schema version: 1

  • settings
    object
    • settings.clusterConfigNamespaces
      string
      Used to manage the cluster scoped resources. For more information see
    • settings.nodeSelector
      object
      The same as in the Pods spec.nodeSelector parameter in Kubernetes. If the parameter is omitted or false, nodeSelector will be determined automatically.
    • settings.resourcesRequests
      object

      Max amounts of CPU and memory resources that the Pod can request when selecting a node.

      If the vertical-pod-autoscaler module is disabled, then these values become the default ones.

      Default: {}

      Examples: 


      mode: VPA
vpa:
  cpu:
    max: 2
    min: 50m
  memory:
    max: 2Gi
    min: 256Mi
  mode: InPlaceOrRecreate

      mode: VPA
vpa:
  cpu:
    max: 3000m
    min: 1
  memory:
    max: 4096
    min: 1024
  mode: Initial

      mode: Static
static:
  cpu: 55m
  memory: 256Ki
      • settings.resourcesRequests.mode
        string

        Required value

        Resource request management mode:

        • Static is a classic one. In it, you explicitly specify requests. The parameters of this mode are defined in the Static parameter section.
        • VPA mode uses VPA. You can configure this mode by modifying parameters in the VPA parameter section.

        Default: VPA

        Allowed values: VPA, Static

      • settings.resourcesRequests.static
        object
        Resource request management options for the Static mode.

        Default: {}

        • settings.resourcesRequests.static.cpu

          Required value

          Configuring CPU requests.

          Default: 150m

        • settings.resourcesRequests.static.memory

          Required value

          Configuring memory requests.

          Default: 256Mi

      • settings.resourcesRequests.vpa
        object
        Resource request management options for the VPA mode.

        Default: {}

        • settings.resourcesRequests.vpa.cpu
          object

          Required value

          CPU-related parameters.

          Default: {}

          • settings.resourcesRequests.vpa.cpu.max
            The maximum value that the VPA can set for the CPU requests.

            Default: 500m

          • settings.resourcesRequests.vpa.cpu.min
            The minimum value that the VPA can set for the CPU requests.

            Default: 100m

        • settings.resourcesRequests.vpa.memory
          object

          Required value

          The amount of memory requested.

          Default: {}

          • settings.resourcesRequests.vpa.memory.max
            The maximum memory requests the VPA can set.

            Default: 768Mi

          • settings.resourcesRequests.vpa.memory.min
            The minimum memory requests the VPA can set.

            Default: 192Mi

        • settings.resourcesRequests.vpa.mode
          string

          Required value

          The VPA usage mode.

          Default: Initial

          Allowed values: Initial, Auto

    • settings.tolerations
      array 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.
      • settings.tolerations.effect
        string
        The taint effect to match. An empty value matches all taint effects.
      • settings.tolerations.key
        string
        The taint key that the toleration applies to. An empty key with the Exists operator matches all keys, values, and effects.
      • settings.tolerations.operator
        string

        The relationship between the taint key and its value.

        With Exists, the toleration matches a taint that has the given key regardless of its value. With Equal, the taint value must also match the value field.

      • settings.tolerations.tolerationSeconds
        integer

        The period, in seconds, that the Pod tolerates the taint before it is evicted. Applies only to taints with the NoExecute effect.

        If the field is omitted, the Pod tolerates the taint indefinitely.

      • settings.tolerations.value
        string
        The taint value that the toleration matches. Leave empty when the operator is Exists.