Install and upgrade pattern
e6data uses thehelm 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.
Kubernetes workloads reference
Platform components (e6operator namespace):
Workspace components (per workspace namespace):
Resource footprint
See also
- Configure registry, VPC, EKS, and networking - where these components are installed.
- Troubleshooting - diagnosing component issues.
- Upgrades and releases - platform upgrade workflow.