Skip to main content
This reference summarizes the Kubernetes resources an In-VPC (CloudPrem) deployment installs and the conventions it follows. For the build steps, see the In-VPC deployment guides for AWS and Azure.

​
Namespaces

​
Custom resource definitions

The e6data operator installs CRDs under e6data.io, including namespaceconfigs, queryrouters, queryservices, metadataservices, monitoringservices, and e6catalogs. Clusters are managed as QueryService resources - see CloudPrem cluster operations.

​
Platform components

​
Conventions

  • A default gp3 StorageClass (AWS) backs persistent volumes.
  • CRDs are applied with kubectl apply --server-side (the combined payload exceeds Helm’s 1 MB release-Secret and 256 KB annotation limits). On AWS the platform and workspace components use the helm template | kubectl apply --server-side pattern; on Azure the operator is installed with helm upgrade and workspace resources are applied as custom resources.
  • Workspace pods are scheduled onto workspace node pools via tolerations and node selectors.

​
See also

Last modified on September 29, 2026