The module does not have any mandatory parameters.
The module is enabled by default in the following bundles: Default, Managed.
The module is disabled by default in the Minimal bundle.
The module is configured using the ModuleConfig custom resource named dashboard (learn more about setting up Deckhouse…).
Example of the ModuleConfig/dashboard resource for configuring the module:
apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: dashboard
spec:
  version: 2
  enabled: true
  settings: # <-- Module parameters from the "Parameters" section below.
Parameters
Schema version: 2
- objectsettings- stringsettings.accessLevelThe level of access to the dashboard if the user-authnmodule is disabled and noexternalAuthenticationis configured. See supported values in the user-authz documentation.By default, Userlevel is used.Use user-authzmodule settings to configure access if theuser-authnmodule is enabled orexternalAuthenticationis configured.Default: "User"Allowed values: User,PrivilegedUser,Editor,Admin,ClusterEditor,ClusterAdmin,SuperAdmin
- objectsettings.authOptions related to authentication or authorization in the application. - booleansettings.auth.allowScaleActivate ability to scale Deployment and StatefulSet from the web interface. This parameter has no effect if the externalAuthenticationis enabled.
- array of stringssettings.auth.allowedUserGroupsAn array of user groups that can access the dashboard. This parameter is used if the user-authnmodule is enabled or theexternalAuthenticationparameter 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.externalAuthenticationParameters to enable external authentication based on the NGINX Ingress external-auth mechanism that uses the Nginx auth_request module. Note! External authentication is enabled automatically if the user-authn module is enabled. - stringsettings.auth.externalAuthentication.authSignInURLThe URL to redirect the user for authentication (if the authentication service returned a non-200 HTTP response code). 
- stringsettings.auth.externalAuthentication.authURLThe URL of the authentication service. If the user is authenticated, the service should return an HTTP 200 response code. 
- booleansettings.auth.externalAuthentication.useBearerTokensThe dashboard must use the user ID to work with the Kubernetes API (the authentication service must return the Authorization HTTP header that contains the bearer-token – the dashboard will use this token to make requests to the Kubernetes API server). Default value is false. Caution! For security reasons, this mode only works if https.mode(global or for a module) is not set toDisabled;
 
- array of stringssettings.auth.whitelistSourceRangesThe CIDR range for which authentication to access the dashboard is allowed. Example: whitelistSourceRanges: - 1.1.1.1/32
 
- booleansettings.highAvailabilityManually 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. Example: highAvailability: true
- objectsettings.httpsWhat certificate type to use with the dashboard. This parameter completely overrides the global.modules.httpssettings.Examples: https: mode: CustomCertificate customCertificate: secretName: foobarhttps: mode: CertManager certManager: clusterIssuerName: letsencrypt- objectsettings.https.certManager- stringsettings.https.certManager.clusterIssuerNameWhat ClusterIssuer to use for the dashboard. Currently, letsencrypt,letsencrypt-staging,selfsignedare available; also, you can define your own.Default: "letsencrypt"
 
- objectsettings.https.customCertificate- stringsettings.https.customCertificate.secretNameThe name of the Secret in the d8-systemnamespace to use with the dashboard (this Secret must have the kubernetes.io/tls format).Default: "false"
 
- stringsettings.https.modeThe HTTPS usage mode: - CertManager— the dashboard will use HTTPS and get a certificate from the ClusterIssuer defined in the- certManager.clusterIssuerNameparameter.
- CustomCertificate— the dashboard will use the certificate from the- d8-systemnamespace for HTTPS.
- Disabled— in this mode, the dashboard works over HTTP only.
- OnlyInURI— the dashboard will work over HTTP (thinking that there is an external HTTPS load balancer in front of it that terminates HTTPS traffic). All the links in the user-authn will be generated using the HTTPS scheme. Load balancer should provide a redirect from HTTP to HTTPS.
 Allowed values: Disabled,CertManager,CustomCertificate,OnlyInURI
 
- stringsettings.ingressClassThe class of the Ingress controller used for the dashboard. 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])?)*$
- objectsettings.nodeSelectorThe same as in the Pods’ spec.nodeSelectorparameter in Kubernetes.If the parameter is omitted or false, it will be determined automatically.
- array of objectssettings.tolerationsThe same as in the Pods’ spec.tolerationsparameter in Kubernetes.If the parameter is omitted or false, it will be determined automatically.- stringsettings.tolerations.effect
- stringsettings.tolerations.key
- stringsettings.tolerations.operator
- integersettings.tolerations.tolerationSeconds
- stringsettings.tolerations.value
 
 
Authentication
user-authn module provides authentication by default. Also, externalAuthentication can be configured (see below). If these options are disabled, the module will use basic auth with the auto-generated password.
Use kubectl to see password:
kubectl -n d8-system exec svc/deckhouse-leader -c deckhouse -- deckhouse-controller module values dashboard -o json | jq '.dashboard.internal.auth.password'
Delete the Secret to re-generate password:
kubectl -n d8-dashboard delete secret/basic-auth
Note! The
auth.passwordparameter is deprecated.