For the complete documentation index, see llms.txt.
Skip to main content

Helm Charts Overview

reShapr components are packaged as four independently versioned Helm charts. This page describes baseline 0.0.15; the reshapr-helm-charts repository owns installation commands, values, and release artifacts.

Prerequisites​

The current charts declare Kubernetes 1.25 or later and require Helm 3.8 or later for OCI support. Installing the controllers also requires cluster-level permissions for CRDs and RBAC.

cert-manager is required when the Web UI uses TLS and when the admission controller uses its default certificate provider. The controllers chart also documents OpenShift and existing-certificate alternatives.

Choose a chart​

ChartRoleTypical placementCanonical documentation
reshapr-control-planeControl plane API and configuration managementCore platform namespaceREADME and commands
reshapr-proxyMCP server and data planeDedicated proxy namespace or close to workloadsREADME and commands
reshapr-web-uiAdministration dashboardPlatform namespace, connected to the control planeREADME and commands
reshapr-controllersKubernetes operator and admission webhookreshapr-system by defaultREADME and commands

Topology choices​

Core platform​

Install the control-plane chart as the platform anchor. It can provision PostgreSQL and the Web UI as optional subcharts, or connect to separately managed instances. Add one or more proxy releases for MCP traffic.

Standalone components​

Install the proxy or Web UI chart independently when their lifecycle, namespace, or scaling must remain separate from the control plane. Both still require connectivity to a running control plane.

Kubernetes-native management​

Install the controllers chart to manage reShapr resources through Kubernetes APIs or inject proxy sidecars through the admission webhook. The operator and admission controller are enabled together by default and can be selected independently.

See Kubernetes APIs and Controllers before choosing this path.

Development and production values​

Each chart directory owns its values.yaml, values-dev.yaml, and values-production.yaml. Use those files as the current source for image tags, resources, replicas, ingress, security contexts, and component-specific settings:

For a reproducible installation, select an immutable version from the Helm chart releases and use documentation and values from the same tag.

Charts 0.0.15 retain the control-plane encryptionKey.activeKeyId and encryptionKey.keys.<kid> values required for AES-256-GCM key rotation. They retain encryptionKey.value and encryptionKey.key only for decrypting legacy AES/ECB values during migration. The Web UI chart sets BODY_SIZE_LIMIT to 12M and allows an explicit override through extraEnv.

The corrected controllers chart 0.0.15 packages all eight controllers 0.0.4 CRDs, including Prompts and ConfigurationPlan toolExposureMode. Its default values still select nightly, while Chart.yaml and installation notes report app version 0.0.1. Pin both controller image tags to 0.0.4 for the reviewed baseline; do not use chart metadata alone to identify the running version. Explicitly update CRDs when upgrading an existing installation.

Runtime tuning and logs​

Use Runtime environment variables for proxy and control-plane settings, including Code Mode guardrails and backend/discovery payload limits. Use Logging for component categories and sensitive-data warnings, and Troubleshooting for rollout commands.

Chart 0.0.15 exposes extraEnv (proxy), ctrl.extraEnv (control plane), operator.extraEnv, and admissionController.extraEnv. User-supplied lists replace defaults: preserve existing telemetry entries, especially the proxy's QUARKUS_OTEL_SDK_DISABLED=true when telemetry is disabled.

Limits​

  • Chart versions are not necessarily identical across all four components; verify each selected release.
  • Controllers chart 0.0.15 packages the baseline CRDs but does not select the baseline controller image without explicit overrides.
  • Helm does not remove CRDs when the controllers chart is uninstalled. Deleting CRDs manually also deletes their custom resources across namespaces.
  • This overview does not duplicate the complete values schema or installation commands. Review the selected chart's owner documentation before deployment.

Next step​

Agent View