Configuration key values for installing Tanzu Mission Control Self-Managed
You use key-values to set up the configuration for installing Tanzu Mission Control Self-Managed.
The following table lists keys and the values that you can use in the values.yaml configuration file for installing Tanzu Mission Control Self-Managed.
| Key | Default | Type | Required | Description |
|---|---|---|---|---|
| alertmanager.criticalAlertReceiver | map[] | No | Critical alert receiver configuration for alert-manager | |
| alertmanager.warningAlertReceiver | map[] | No | Warning alert receiver configuration for alert-manager | |
| clusterIssuer | string | Yes | Cert-Manager ClusterIssuer to use. This must be pre-created in the tmc-local namespace. | |
| contourEnvoy.loadBalancerIP | string | No | Load balancer IP for Contour’s Envoy. This is the legacy way to use a preferred IP for a K8s serivce of type loadBalancer and is deprecated from Kubernetes version 1.24 onwards. |
|
| contourEnvoy.loadBalancerClass | string | No | Load Balancer Class to use for Contour’s Envoy | |
| contourEnvoy.nodeSelector | No | Node Label Selectors for Contour’s Envoy pod assignment | ||
| contourEnvoy.nodeTolerations | array | No | Tolerations for Contour’s Envoy pod assignment | |
| contourEnvoy.serviceAnnotations | No | Annotations to place on Contour’s Envoy Pods. Your load balancer controller specific annotations to use a preferred IP. See Service of type loadBalancer with preferred IP for a AVI Kubernetes Operator. | ||
| contourEnvoy.serviceType | string | Yes | Service Type for Contour’s Envoy. Must be one of Loadbalancer or NodePort. | |
| dnsZone | string | Yes | Hosted DNS zone where the DNS A-records for Tanzu Mission Control Self-Managed service will reside in | |
| harborProject | string | Yes | Harbor Project path where Tanzu Mission Control Self-Managed service images have been pushed to using the push-images command. E.g., harbor.tanzu.io/tmc |
|
| minio.password | string | Yes | Admin password to use for internal Minio | |
| minio.username | string | Yes | Admin username to use for internal Minio | |
| oidc.clientID | string | Yes | OIDC Client ID defined in your IDP | |
| oidc.clientSecret | string | Yes | OIDC Client Secret defined in your IDP | |
| oidc.issuerType | string | Yes | OIDC issuer type. pinniped is the only supported option currently. |
|
| oidc.issuerURL | string | Yes | OIDC issuer URL for your IDP | |
| pinnipedExtraEnvVars | [] | array | No | Extra Environment Variables to pass to Pinniped |
| postgres.userPassword | string | Yes | Password to use for securing internal Postgres connections | |
| postgres.maxConnections | 300 | integer | No | Max Connections the internal Postgres database should allow. This should only be changed in consultation with VMware support. |
| prometheusVolumeSize | 5Gi | string | Yes | Persistent volume size for Prometheus data volume - generally given in Gibibytes (100Gi) |
| supportFlags | [] | array | No | Flags a support engineer may ask you to add if you need support |
| telemetry.eanNumber | string | No | Entitlement Account Number on VMware Customer Connect | |
| telemetry.ceipAgreement | false | boolean | No | Indicates that you have read the CEIP terms and conditions through the product documentation |
| telemetry.ceipOptIn | false | boolean | No | CEIP Opt in to send telemetry data |
| trustedCAs | map[] | No | Adds trusted CAs (in pem format) to the bundle used by services. This should be in a key value form |
