RPI v7.7 and later
The RPI v7.7 Helm chart has been enhanced so you never need to fork or edit the Helm chart. All customization is done through your overrides file, which is typically 50-100 lines. Chart updates apply automatically without reconciling template changes.
If you’re upgrading from RPI v7.6, there are some additional considerations. Refer to Upgrading to RPI v7.7 for details.
Update process
Generate or update your overrides using the RPI Helm Assistant. Use the Reference tab to browse available configuration options, or the Chat tab to ask questions about specific features. When upgrading between chart versions, see the Migration readme for details on key changes, new features, and any breaking changes.
Why you don't need to fork
-
Internal defaults (probes, security contexts, logging, ports, rollout strategies) are chart-managed
-
All enterprise features (annotations, CSI secrets, image overrides, CA certs, Karpenter, service mesh) are configurable through values
-
New chart defaults apply automatically on upgrade without any action on your part
-
The Reference tab shows every configurable key so you know exactly what you can override
When a new RPI version is released, update the global.deployment.images.tag in your overrides and redeploy. To see the full list of images:
helm template rpi ./chart -f overrides.yaml | grep "image:" | sort -u
Custom requirements
If your deployment has specific requirements that cannot be achieved through the overrides file (e.g., organizational policies, compliance constraints, or unique infrastructure patterns), contact support@redpointglobal.com with your use case. We incorporate customer requirements as native chart features so you never need to maintain forked templates. All enterprise features in v7.7 (custom annotations, CSI secrets, image overrides, CA certificates, Karpenter, service mesh, smoke tests) were built this way.