Configure Installation
This page explains how to configure the installation of Control Center using Helm. You can set many values, including your domain and user information.
Setting Configuration Values
Below is an example using the Helm command to configure several values. You would change the values in the example to your particular use.
helm install control-center-name oci://docker.io/vaadin/control-center \ 1
-n foo-namespace --create-namespace \ 2
--set domain=mydomain.com \ 3
--set user.email=example@mydomain.com \ 4
--set app.host=cc.mydomain.com \ 5
-f values-ingress.yaml \ 6
--wait
-
The name of the installed application is set to
control-center-name
. -
The namespace in which the application is installed is set to
foo-namespace
. -
The required value of
domain
is set tomydomain.com
. -
The required value of
user.email
is set toexample@mydomain.com
. -
The optional value of
app.host
is set tocc.mydomain.com
. -
The values for the Ingress are set using a file named
values-ingress.yaml
.
More command options, than the ones shown in the example above, are available for configuring the installation. All options are explained in detail in the Helm documentation.
List of Values
The following table lists the available values and their descriptions. Each of the values can be set using the --set
flag when installing Control Center using Helm.
Value | Required | Default | Description |
---|---|---|---|
| Yes | The domain name of the Control Center installation. This is used to generate the host names for Control Center and Keycloak. | |
| Yes | The email address of the Control Center administrator user. | |
| No | Replace every occurrence of "control-center". | |
| No | The full name is generated as "control-center" if the release name is "control-center". However, if the release name is "foo", the full name is "foo-control-center". This value overrides the full name. | |
| No |
| Specifies whether a service account should be created. |
| No |
| Specifies whether to automount the service account token. |
| No | The name of the service account to use. | |
| No | Annotations to add to the service account. | |
| No | The host name of the Control Center application. If none is specified, | |
| No | The name of the secret with the | |
| No |
| The image repository to use for the Control Center application. |
| No | The pull policy to use for the image. If none is specified, the Kubernetes default is used. | |
| No | The image tag to use for the Control Center application. If none is specified, the chart’s | |
| No | The image pull secrets to use for the Control Center application. | |
| No | Extra labels to add to the Control Center application pods. | |
| No | Extra annotations to add to the Control Center application pods. | |
| No | The security context for the Control Center application pods. | |
| No | The security context for the Control Center application deployment. | |
| No |
| The number of replicas for the Control Center application. |
| No |
| Specifies whether |
| No |
| The minimum number of replicas for the Control Center application. |
| No |
| The maximum number of replicas for the Control Center application. |
| No |
| The target CPU utilization percentage for the Control Center application. |
| No |
| The target memory utilization percentage for the Control Center application. |
| No | The resource to allocate for the Control Center application containers. | |
| No |
| The path to use for the startup probe for the Control Center application. |
| No |
| The port to use for the startup probe. |
| No |
| The initial delay in seconds for the startup probe. |
| No |
| The failure threshold for the startup probe. If the probe fails this many times, the container is restarted. |
| No |
| The path to use for the liveness probe for the Control Center application. |
| No |
| The port to use for the liveness probe. |
| No |
| The initial delay in seconds for the liveness probe. |
| No |
| The failure threshold for the liveness probe. If the probe fails this many times, the container is restarted. |
| No |
| The path to use for the readiness probe for the Control Center application. |
| No |
| The port to use for the readiness probe. |
| No |
| The initial delay in seconds for the readiness probe. |
| No |
| The failure threshold for the readiness probe. |
| No | The volume definitions for the Control Center application. | |
| No | The volume mounts for the Control Center application. | |
| No | The custom node selectors for the Control Center application. | |
| No | The custom | |
| No | The custom affinity for the Control Center application. | |
| No |
| The type of service to create for the Control Center application. |
| No |
| The port to expose for the Control Center application. |
| No |
| The port for the Control Center application containers. |
| No |
| Specifies whether to create an Ingress for the Control Center application. |
| No | The annotations to add to the Ingress. | |
| No | The hosts to add to the Ingress. If none is specified, | |
| No | The TLS configuration for the Ingress. | |
| No |
| The number of replicas for the PostgreSQL database. |
| No |
| The storage size for the PostgreSQL database. |
| No |
| The image repository to use for the Keycloak instance. |
| No | The image tag to use for the Keycloak instance. If none is specified, the chart’s | |
| No | The resources to allocate for the Keycloak containers. | |
| No | The hosts for the Keycloak instance. If none is specified, | |
| No | The name of the secret with the keystore for the Keycloak instance. | |
| No |
| Specifies whether to enable ACME for the Ingress. When enabled, certificates are automatically requested from |
| No |
| The ACME server to use. |
| No |
| Specifies whether to enable the Keycloak Operator. |
| No |
| The image repository to use for the Keycloak Operator. |
| No |
| Specifies whether to enable Cloud Native PostgreSQL Operator. |
| No |
| Specifies whether to create the Custom Resource Definitions (CRD) for the Operator. |
| No |
| Specifies whether to enable the Ingress NGINX Controller. |
| No |
| Specifies whether to enable the scope for the Ingress NGINX Controller. |
| No |
| Specifies whether to enable CertManager. |
| No |
| Specifies whether to enable the certificate owner reference for CertManager. |
| No |
| Specifies whether to enable ExternalDNS |
| No |
| Specifies whether ExternalDNS should be namespaced. |
| No |
| The TXT owner ID for ExternalDNS. |
| No |
| The sources for ExternalDNS. |