Skip to main content
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.
This reference applies to In-VPC deployments only. Always use the values template and image versions provided by your e6data onboarding engineer.

​
Operator chart

​
Workspace components

On AWS these are Helm values; on Azure they are the equivalent fields on the NamespaceConfig and QueryRouter resources. 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 and Azure.

​
See also

Last modified on September 29, 2026