| ingress | object | {…} | Ingress configuration |
| ingress.istio | object | {…} | Istio ingress configuration |
| ingress.istio.gateway.annotations | object | {} | Additional gateway annotations |
| ingress.istio.gateway.labels | object | {} | Additional gateway labels |
| ingress.istio.internalDNSResolution.enabled | bool | false | indicates whether we should set up resources in Istio so that calls within the mesh to the vantage cluster FQDN are routed back through the ingress gateway (set this to true if vantage.DNSRecord does not actually have a public DNS record). (requires DNS Proxying) |
| ingress.kubernetes | object | {…} | Native Kubernetes Ingress configuration |
| ingress.kubernetes.annotations | object | {} | Additional ingress annotations |
| ingress.kubernetes.ingressClassName | string | "" | Defines which ingress controller will implement the resource |
| ingress.kubernetes.labels | object | {} | Additional ingress labels |
| ingress.kubernetes.nginx | bool | false | Set to true if using an ingress class not named “nginx” that implements nginx features (e.g. AKS web app routing) |
| ingress.tls.enabled | bool | true | Whether the ingress terminates TLS with a Kubernetes secret. Set to false when the ingress controller supplies the certificate out of band (e.g. an ACM certificate attached to the AWS ALB IngressClassParams). |
| ingress.type | string | "istio" | Ingress implementation. One of kubernetes or istio. |
| mesh | object | {…} | Service mesh configuration |
| mesh.istio.enabled | bool | true | Set to true to deploy recommended Istio mesh config. |
| observability | object | {…} | Observability configuration |
| observability.prometheus | object | {…} | Prometheus observability configuration |
| observability.prometheus.namespace | string | "observability" | Namespace in which Prometheus instance is installed |
| observability.prometheus.serviceMonitor | object | {…} | Prometheus ServiceMonitor configuration |
| observability.prometheus.serviceMonitor.create | bool | false | whether to create a Prometheus ServiceMonitor to scrape Vantage application metrics |
| observability.prometheus.serviceMonitor.selectorMatchLabels | object | {} | any labels required by Prometheus to register a ServiceMonitor (should match your Prometheus CR’s spec.serviceMonitorSelector.matchLabels) |
| operator.controllerManagerServiceAccount | string | "vantage-operator-controller-manager" | |
| operator.namespace | string | "vantage-operator-system" | |
| vantage | object | {…} | Vantage CR spec - these values are passed directly to the Vantage custom resource |
| vantage.databaseProvider | string | "SqlServer" | Database engine used by all Vantage services. One of “SqlServer” or “PostgreSQL”. Case-sensitive: the value is passed straight to each service’s *Database__Provider and must match the runtime DataProvider name exactly (“PostgreSQL”, not “Postgresql”/“PostgreSql”). |
| vantage.dnsRecord | string | "" | DNS record for the Vantage installation |
| vantage.keda | object | {…} | KEDA configuration |
| vantage.keda.enabled | bool | false | Whether to use KEDA for autoscaling |
| vantage.mailFrom | string | "" | Email address used as sender for outgoing emails |
| vantage.ociMigration | object | {…} | OCI migration configuration (optional, omit or set enabled: false to skip) |
| vantage.ociMigration.concurrency | int | 5 | Number of artifacts to copy in parallel |
| vantage.ociMigration.destination | object | {…} | Destination container registry (customer’s registry for mirrored images) |
| vantage.ociMigration.destination.host | string | "abbyy.com" | Registry hostname |
| vantage.ociMigration.destination.password | string | "" | Password for authentication (use credentialsRef for production) |
| vantage.ociMigration.destination.username | string | "" | Username for authentication (use credentialsRef for production) |
| vantage.ociMigration.enabled | bool | true | Enable OCI migration |
| vantage.ociMigration.sources | list | […] | Source registry where Vantage images are pulled from |
| vantage.ociMigration.sources[0] | object | {…} | Registry hostname |
| vantage.ociMigration.sources[0].password | string | "" | Password for authentication (use credentialsRef for production) |
| vantage.ociMigration.sources[0].username | string | "" | Username for authentication (use credentialsRef for production) |
| vantage.platformAdminEmail | string | "" | Email address of the platform administrator |
| vantage.reverseProxy | bool | false | Whether to configure Vantage to run behind a reverse proxy that terminates TLS. |
| vantage.secrets | object | {} | Secrets configuration (exactly one provider must be set: kubernetes or azure). |
| vantage.techcore | object | {…} | TechCore processing engine configuration |
| vantage.techcore.nnTrainingWorkers | object | {…} | Neural network training workers configuration |
| vantage.techcore.nnTrainingWorkers.enabled | bool | false | Enable neural network training workers |
| vantage.techcore.nnTrainingWorkers.gpu | bool | false | Enable GPU acceleration for training workers |
| vantage.techcore.versions | list | [3,4] | TechCore versions to deploy (available versions are 2, 3, 4). |
| vantage.updatePolicy | object | {…} | Update policy for Vantage upgrades |
| vantage.updatePolicy.manual | object | {} | Manual upgrades only (install a new operator Helm chart version to upgrade) |
| vantage.vantageVersion | string | "" | Version of Vantage to install |
| vantage.workloads | object | {…} | Workloads ConfigMap configuration |
| vantage.workloads.configMap | string | "vantage-workloads" | ConfigMap name (if workloadsConfigMap.create is true (which is the default), this value will be used as a prefix for the created ConfigMap’s name.) |
| vantage.workloads.metadataTemplateKey | string | "workloads-metadata.yml.gotmpl" | Workloads metadata template key |
| vantage.workloads.secretsKey | string | "workloads-secrets.yml.gotmpl" | Workloads secrets key |
| vantage.workloads.workloadsKey | string | "workloads.yml" | Workloads key |
| workloadsConfigMap.create | bool | true | Whether to create the ConfigMap containing data about charts and images required to install vantage. When this option is true, deploying a new chart version will update the Vantage custom resource itself, effectively updating Vantage in-place (works under both helm install/helm upgrade and GitOps tools that render with helm template, e.g. ArgoCD/Flux). |