> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/reference/configuration-reference/helm-values.md).

# 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.

{% hint style="info" %}
This reference applies to In-VPC deployments only. Always use the values template and image versions provided by your e6data onboarding engineer.
{% endhint %}

## 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](/query-engine/guides/deployment/aws-in-vpc/deploy-workspace-and-e6data.md) and [Azure](/query-engine/guides/deployment/azure-in-vpc/deploy-workspace-and-e6data.md).

## See also

* [Configure registry, VPC, EKS, and networking (AWS)](/query-engine/guides/deployment/aws-in-vpc/configure-registry-vpc-eks-networking.md)
* [Component versions and operations (AWS)](/query-engine/guides/deployment/aws-in-vpc/component-versions-and-operations.md) · [Azure](/query-engine/guides/deployment/azure-in-vpc/component-versions-and-operations.md)
* [Environment variables](/query-engine/reference/configuration-reference/environment-variables.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/reference/configuration-reference/helm-values.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.