The delivery module: configuration

This feature is available in Enterprise Edition only.

The module is not enabled by default in any bundles.

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

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

Use the delivery 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 delivery module:

          apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: delivery
spec:
  enabled: true

        

Example of disabling the delivery module:

          apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: delivery
spec:
  enabled: false

        

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

Example of the ModuleConfig/delivery resource for configuring the module:

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

Parameters

Schema version: 1

argocdobject
Argo CD configuration.
- argocd.adminobject
  - argocd.admin.enabledboolean
    Enables Argo CD admin user.
    
    Might be helpful when Dex is not used or for argocd CLI access (read the Usage article for more information).
    
    Default: false
httpsobject
What certificate type to use with Argo CD web-interface.

This parameter completely overrides the global.modules.https settings.

Examples:
```
https:
  mode: CustomCertificate
  customCertificate:
    secretName: foobar
```
```
https:
  mode: CertManager
  certManager:
    clusterIssuerName: letsencrypt
```
- https.certManagerobject
  - https.certManager.clusterIssuerNamestring
    What ClusterIssuer to use for Argo CD web-interface.
    
    Currently, letsencrypt, letsencrypt-staging, selfsigned are available. Also, you can define your own.
    
    Default: "letsencrypt"
- https.customCertificateobject
  - https.customCertificate.secretNamestring
    The name of the secret in the d8-system namespace to use with Argo CD web-interface.
    
    This secret must have the kubernetes.io/tls format.
    
    Default: "false"
- https.modestring
  The HTTPS usage mode:
  - Disabled — Argo CD web-interface will work over HTTP only;
  - CertManager — Argo CD web-interface will use HTTPS and get a certificate from the clusterissuer defined in the certManager.clusterIssuerName parameter.
  - CustomCertificate — Argo CD web-interface will use HTTPS using the certificate from the d8-system namespace.
  - OnlyInURI — Argo CD web-interface will work over HTTP (thinking that there is an external HTTPS load balancer in front that terminates HTTPS traffic). All the links in the user-authn will be generated using the HTTPS scheme.
  Default: "Disabled"
  Allowed values: Disabled, CertManager, CustomCertificate, OnlyInURI
nodeSelectorobject
Node selector for the Argo CD server. 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
```
storageClass
The name of the StorageClass to use.

If omitted, the StorageClass of the existing PVC is used. If there is no PVC yet, either the global StorageClass or global.discovery.defaultStorageClass is used, and if those are undefined, the emptyDir volume is used to store the data.

CAUTION! Setting this value to one that differs from the current one (in the existing PVC) will result in disk reprovisioning and data loss.

Setting it to false forces the use of an emptyDir volume.

Examples:
```
storageClass: false
```
```
storageClass: default
```
tolerationsarray of objects
Node tolerations for the Argo CD server. 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