Configuration
This section contains the …
-
configuration that is shared between components,
-
and configuration of each component.
These variables are configured by the operator. There are different options available to choose from for some components. Only the corresponding variables of the chosen component have to be configured. Typical deployment scenarios either always use the first or the second option for mutual TLS authentication and key-value store.
-
For mutual TLS authentication there are two configuration options:
| Option | Description | Chapter |
|---|---|---|
Kubernetes NGINX Ingress Controller |
The Kubernetes Ingress Controller is used. |
|
Deploying an NGINX |
A self-hosted NGINX component is deployed. |
-
Device Portal requires a key-value store which can be provided in two ways:
| Option | Description | Chapter |
|---|---|---|
Using an external Redis |
An external Redis Cache instance is used. |
|
Using a Valkey within the cluster |
A high available Valkey Sentinel which is deployed as part of the cluster. |
-
The Artifact Repository provided by the Device Portal can be deployed in two ways:
| Option | Description | Chapter |
|---|---|---|
Managed Artifact Repository |
Typically, it will be deployed in form of a "Managed Artifact Repository" which supports multi-tenancy and is deployed as part of the Device Portal. |
|
Private Artifact Repository |
In an installation with internet connectivity it is possible to connect multiple customer-specific Private Artifact Repository instances (operated by the customers in Azure Cloud) in addition. |
-
If the Device Portal is deployed via its own umbrella chart, the following additional configurations have to be made:
| Module | Description | Chapter |
|---|---|---|
Portal configuration |
Configuration where the Portal module is located & reachable |
Portal-Configuration_for_Device-Portal_Umbrella_chart_deployment |
Macma configuration |
Configuration where the Macma module is located & reachable |
Macma-Configuration_for_Device-Portal_Umbrella_chart_deployment |
Ansible Operator configuration |
Configuration of the Ansible Operator namespace (must be in same cluster) |
AnsibleOperator-Configuration_for_Device-Portal_Umbrella_chart_deployment |