> 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/kubernetes-configuration.md).

# Kubernetes configuration

Reference for the Kubernetes resources an In-VPC e6data deployment installs - CRDs, storage class, node provisioning, and namespaces.

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](/query-engine/guides/deployment/aws-in-vpc/configure-registry-vpc-eks-networking.md) and [Azure](/query-engine/guides/deployment/azure-in-vpc/configure-registry-kubernetes-networking.md).

## Namespaces

| Namespace      | Contents                                                            |
| -------------- | ------------------------------------------------------------------- |
| `e6operator`   | The e6data operator and its CRDs                                    |
| `cert-manager` | cert-manager components                                             |
| `<workspace>`  | Per-workspace components (console, query router, metadata services) |

## 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](/query-engine/guides/clusters/cloudprem-cluster-operations.md).

## Platform components

| Component                          | Role                                                                        |
| ---------------------------------- | --------------------------------------------------------------------------- |
| e6data operator                    | Reconciles e6data CRDs into running workloads                               |
| cert-manager                       | TLS certificate lifecycle                                                   |
| Karpenter                          | Node provisioning via NodePool - EC2NodeClass on AWS, AKSNodeClass on Azure |
| AWS Load Balancer Controller (AWS) | Provisions load balancers for ingress                                       |

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

* [CloudPrem cluster operations](/query-engine/guides/clusters/cloudprem-cluster-operations.md)
* [AWS configuration](/query-engine/reference/configuration-reference/aws-configuration.md) · [Azure configuration](/query-engine/reference/configuration-reference/azure-configuration.md)
* [Helm values](/query-engine/reference/configuration-reference/helm-values.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/kubernetes-configuration.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.