> 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/guides/deployment/aws-in-vpc/component-versions-and-operations.md).

# Component versions and operations

The Kubernetes workloads an In-VPC e6data deployment runs, the resource footprint, and the operational pattern for installs and upgrades.

This page summarizes what an In-VPC deployment runs and how to operate it.

## Install and upgrade pattern

e6data uses the `helm template | kubectl apply --server-side` pattern instead of `helm install`. This avoids Helm's 1 MB release Secret limit and gives clean field-manager handling during upgrades. To upgrade a component, re-render its chart with the new image tags (provided by e6data) and re-apply with `kubectl apply --server-side --force-conflicts`.

Image versions and chart versions for each release come from your e6data onboarding engineer - see the items listed in [Prerequisites](/query-engine/guides/deployment/aws-in-vpc/prerequisites.md).

## Kubernetes workloads reference

**Platform components (`e6operator` namespace):**

| Kind       | Name                                                                    | Description                                        |
| ---------- | ----------------------------------------------------------------------- | -------------------------------------------------- |
| Deployment | `e6operator`                                                            | Controller managing all e6data CRDs.               |
| Service    | `e6operator-webhook-service`                                            | Admission webhook for custom-resource validation.  |
| Deployment | `cert-manager` (plus `cert-manager-webhook`, `cert-manager-cainjector`) | Issues the operator's webhook serving certificate. |
| Deployment | `karpenter` (in `kube-system`)                                          | Provisions e6operator and engine nodes.            |

**Workspace components (per workspace namespace):**

| Kind       | Name                                           | Description                                                                |
| ---------- | ---------------------------------------------- | -------------------------------------------------------------------------- |
| Deployment | `console`                                      | Web console UI and backend.                                                |
| Deployment | `<workspace>-qr-envoy`                         | Query routing proxy (TLS termination, JWT enforcement).                    |
| Deployment | `<workspace>-qr-xds`                           | Dynamic routing configuration for Envoy.                                   |
| Deployment | `mds-schema` / `mds-storage`                   | Metadata services (created on demand).                                     |
| DaemonSet  | `o11y-collector` (`vector` / `metrics-bridge`) | Workspace log and metrics collection (when MonitoringServices is enabled). |
| CronJob    | `compaction`                                   | Metadata compaction job.                                                   |
| Service    | `<workspace>-qr-envoy-external`                | LoadBalancer for query and console traffic.                                |

## Resource footprint

| Category                  | Cluster-level                                                         | Per workspace                     |
| ------------------------- | --------------------------------------------------------------------- | --------------------------------- |
| VPC and networking        | \~15 resources (VPC, subnets, NAT Gateway, route tables, S3 endpoint) | 1 Load Balancer                   |
| EKS                       | 1 cluster + system node group                                         | -                                 |
| IAM roles                 | 4–5 (cluster, node, Karpenter, ALB, EBS CSI)                          | 3 (engine, console, app)          |
| S3 buckets                | -                                                                     | 1 (metadata)                      |
| Pod Identity associations | 2–3 (Karpenter, ALB, EBS CSI)                                         | 5                                 |
| EC2 instances             | 2 (system nodes)                                                      | 0–N (engine nodes, scale to zero) |
| NodePools                 | 1 (e6operator)                                                        | 1                                 |
| EC2NodeClasses            | 1 (e6operator)                                                        | 1                                 |

## See also

* [Configure registry, VPC, EKS, and networking](/query-engine/guides/deployment/aws-in-vpc/configure-registry-vpc-eks-networking.md) - where these components are installed.
* [Troubleshooting](/query-engine/guides/deployment/aws-in-vpc/troubleshooting.md) - diagnosing component issues.
* [Upgrades and releases](/query-engine/guides/operations/upgrades-and-releases.md) - platform upgrade workflow.


---

# 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/guides/deployment/aws-in-vpc/component-versions-and-operations.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.