Available with limitations in: CE, BE, SE
Available without limitations in: SE+, EE
parameters
Schema version: 1
-
-
objectsettings.authAuthentication configuration.
Default:
{}-
array of stringssettings.auth.allowedUserGroups
An array of user groups that can access the web UI.
This parameter is used if the user-authn module is enabled or the
externalAuthenticationparameter is set.Caution! Note that you must add those groups to the appropriate field in the DexProvider config if this module is used together with the user-authn one.
-
objectsettings.auth.externalAuthentication
Parameters to enable external authentication. Uses Nginx Ingress external-auth mechanism which is based on the the Nginx auth_request module.
Note! External authentication is enabled automatically if the user-authn module is enabled.
Default:
{}-
stringsettings.auth.externalAuthentication.authSignInURLURL to redirect the user for authentication (if the authentication service returned a non-200 HTTP response code).
-
stringsettings.auth.externalAuthentication.authURLURL of the authentication service. If the user is authenticated, the service should return an HTTP 200 response code.
-
-
stringsettings.auth.passwordDeprecated
This parameter is ignored and will be removed in future releases.
It was used for http authorization of the
adminuser, if the user-authn module was disabled or theexternalAuthenticationparameter was not set.Now the external authentication is required for Deckhouse Commander to function properly.
-
array of stringssettings.auth.whitelistSourceRangesAn array if CIDRs that are allowed to authenticate.
Example:
whitelistSourceRanges: - 1.1.1.1/32
-
-
objectsettings.featureFlagsA parameter used to control experimental features.
Default:
{} -
booleansettings.highAvailability
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: truehighAvailability: false -
objectsettings.https
What certificate type to use with the web UI.
This parameter completely overrides the
global.modules.httpssettings.Examples:
customCertificate: secretName: foobar mode: CustomCertificatecertManager: clusterIssuerName: letsencrypt mode: CertManager-
objectsettings.https.certManager
Default:
{}-
stringsettings.https.certManager.clusterIssuerName
What ClusterIssuer to use for the web UI.
Currently,
letsencrypt,letsencrypt-staging,selfsignedare available. Also, you can define your own.Default:
letsencrypt
-
-
objectsettings.https.customCertificate
Default:
{}-
stringsettings.https.customCertificate.secretName
The name of the secret in the
d8-systemnamespace to use with the web UI.This secret must have the kubernetes.io/tls format.
Default:
false
-
-
stringsettings.https.mode
The HTTPS usage mode:
Disabled— in this mode, the web UI can only be accessed over HTTP. Caution! This mode is not supported. HTTPS is required for the module to function properly. If HTTPS is disabled, the web UI will be unavailable.CertManager— the web UI is accessed over HTTPS using a certificate obtained from a clusterIssuer specified in thecertManager.clusterIssuerNameparameter.CustomCertificate— the web UI is accessed over HTTPS using the certificate from thed8-systemnamespace.OnlyInURI— the web UI will work over HTTP (thinking that there is an external HTTPS load balancer in front that terminates HTTPS traffic). All the links in theuser-authnwill be generated using the HTTPS scheme. Load balancer should provide a redirect from HTTP to HTTPS.
Allowed values:
Disabled,CertManager,CustomCertificate,OnlyInURI
-
-
stringsettings.ingressClass
The class of the Ingress controller used for the web UI.
An optional parameter. By default, the
modules.ingressClassglobal value is used.Pattern:
^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$Example:
ingressClass: nginx -
objectsettings.nodeSelector
The same as in the Pods’
spec.nodeSelectorparameter in Kubernetes.If the parameter is omitted or
false, it will be determined automatically.Example:
disktype: ssd -
objectsettings.postgres
Default:
{}-
objectsettings.postgres.external
-
stringsettings.postgres.external.dbDatabase name
-
stringsettings.postgres.external.hostServer address. You can specify multiple addresses separated by commas if your PostgreSQL cluster consists of multiple nodes. For example:
host1,host2,host3. In this case, you will need to specify a separate port for each node. -
stringsettings.postgres.external.passwordUser password
-
stringsettings.postgres.external.portServer port. If your PostgreSQL cluster consists of multiple nodes and you have specified several nodes, you need to provide a port for each node, separated by commas. For example:
5432,5432,5433 -
objectsettings.postgres.external.ssl
-
stringsettings.postgres.external.ssl.secretName
The name of the secret in the
d8-commandernamespace which contains client certificate for certificate authentication on the PostgreSQL server.Example of creating a secret:
kubectl -n d8-commander create secret generic postgres-ssl --from-file=tls.crt=client.crt --from-file=tls.key=client.key --from-file=ca.crt=ca.crt
-
-
stringsettings.postgres.external.userUser name
-
-
objectsettings.postgres.internal
Default:
{}-
integersettings.postgres.internal.diskSizeGigabytes
Disk size for PostgreSQL database in gigabytes.
You should manually specify the desired disk size for the PostgreSQL database, but you can increase it later if necessary.
The extended-monitoring module automatically monitors the percentage of used disk space.
CAUTION! If the PostgreSQL data storage becomes full, the application may stop working.
Default:
10 -
stringsettings.postgres.internal.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.defaultStorageClassis used.Refer to the documentation section Changing the storage class if you want to change this value.
Examples:
storageClass: ceph-ssdstorageClass: network-ssd
-
-
stringsettings.postgres.mode
The PostgreSQL usage mode:
-
Internal— PostgreSQL is deployed in a cluster and managed using the postgres-operator.This is not a recommended method for use in production environments. However, the use of
operator-postgresis convenient for quick start with Deckhouse Commander or for environments where there are no high availability and support requirements. -
External- an external PostgreSQL installation managed by the user is used. This is the recommended way to use Deckhouse Commander in production environments.
Default:
InternalAllowed values:
Internal,External -
-
-
array of objectssettings.tolerations
The same as in the Pods’
spec.tolerationsparameter in Kubernetes;If the parameter is omitted or
false, it will be determined automatically.Example:
tolerations: - effect: NoSchedule key: key1 operator: Equal value: value1-
stringsettings.tolerations.effect
-
stringsettings.tolerations.key
-
stringsettings.tolerations.operator
-
integersettings.tolerations.tolerationSeconds
-
stringsettings.tolerations.value
-
-