> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Helm values

> Reference for the key Helm values used to deploy the e6data operator and workspace components In Your VPC.

For In-VPC (CloudPrem) deployments, the e6data **operator** is installed with a Helm chart your onboarding engineer provides (once per cluster). Workspace components are deployed per workspace - on **AWS** through an **e6-workspace** Helm chart, and on **Azure** by applying the `NamespaceConfig` and `QueryRouter` custom resources directly. This page summarizes the values (AWS) and equivalent CR fields (Azure) you most commonly set. The complete, version-specific templates ship with the charts.

<Info>
  This reference applies to In-VPC deployments only. Always use the values template and image versions provided by your e6data onboarding engineer.
</Info>

## Operator chart

| Value | Description |
| - | - |
| `image.repository`, `image.tag` | The operator image, provided by e6data |
| `replicaCount` | Operator replicas (typically 2) |
| `resources.requests` / `resources.limits` | CPU and memory for the operator |
| `logLevel` | Operator log level (for example, `info`) |
| `tolerations` | Tolerations so the operator schedules onto its node pool |

## Workspace components

On AWS these are Helm values; on Azure they are the equivalent fields on the `NamespaceConfig` and `QueryRouter` resources.

| Value / field | Description |
| - | - |
| `workspaceName` | The workspace name |
| `tenant` | Your tenant identifier (from onboarding) |
| `cloud`, `region` | Cloud provider and region |
| `storageBackend` | The metadata storage bucket/account |
| `imageRepository` | The image repository for workspace components |
| `namespaceConfig.*` | Console, compaction, node pool, and tolerations for the workspace |
| `queryRouter.*` | Envoy, XDS, HTTP/PG query settings, TLS, and JWT auth |
| `monitoringServices.*` | Monitoring endpoint and credentials (if monitoring is enabled) |

On AWS these values are rendered with `helm template | kubectl apply --server-side`; on Azure the equivalent fields are set directly on the custom resources. See the In-VPC deployment guides for [AWS](/platform/deploy/aws-cloudprem/deploy-workspace) and [Azure](/platform/deploy/azure-cloudprem/deploy-workspace).

## See also

* [Configure registry, VPC, EKS, and networking (AWS)](/platform/deploy/aws-cloudprem/configure-registry-vpc-eks-networking)
* [Component versions and operations (AWS)](/platform/deploy/aws-cloudprem/component-versions-and-operations) · [Azure](/platform/deploy/azure-cloudprem/component-versions-and-operations)
* [Environment variables](/platform/reference/config/environment-variables)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.