Key | Description | Required | Values | ||
---|---|---|---|---|---|
| |||||
YAML schema version. | ✓ |
| |||
| |||||
Unique deployment name. This must contain the name of the deployment owner. | ✓ |
| |||
| |||||
Domino version to install. | ✓ | Supported versions: | |||
| |||||
Hostname Domino application will be accessed at. | ✓ | Valid fully qualified domain name (FQDN) | |||
| |||||
Should Domino only be accessible with HTTPS. | ✓ |
| |||
| |||||
Should Domino only be accessible with HTTPS. | ✓ |
| |||
| |||||
Create Kubernetes resource requests and limits for services. | ✓ |
| |||
| |||||
Use network policies for fine-grained service access. | ✓ |
| |||
| |||||
A URL to ECR (Amazon Elastic Container Registry), ACR (Azure Container Registry), GCR (Google Container Registry) or GAR (Google Artifact Registry). The node must have permissions to the registry. |
| ||||
| |||||
✓ | |||||
| |||||
Use the minimum amount of nodes and resources to run Domino. This may not be a stable configuration and should be used with caution. |
| ||||
| |||||
The Kubernetes cluster domain name. |
| ||||
| |||||
AWS account ID in which Domino is deployed. | |||||
| |||||
IAM role arn. | |||||
| |||||
Kubernetes service account name. |
This section configures how and if an Istio Service Mesh is deployed by or integrated to Domino. A Domino-deployed Istio is for Domino use only. These configurations must only be installed and/or enabled if intra-cluster encryption in transit is required.
Key | Description | Required | Values |
---|---|---|---|
| |||
Enable Istio in deployment (that is, sidecar injection). | ✓ |
| |
| |||
Install Istio service with Domino. |