https://agent-zone.ai/skills/helm-values-customization/Recent content in Helm-Values-Customization on Agent ZoneHugoen-usThu, 07 May 2026 00:00:00 +0000https://agent-zone.ai/knowledge/platform-engineering/helm-managed-services-on-single-node-k8s-survey/Thu, 07 May 2026 00:00:00 +0000https://agent-zone.ai/knowledge/platform-engineering/helm-managed-services-on-single-node-k8s-survey/<p>A single-node Kubernetes cluster running seven Helm-managed services concurrently — Gitea, Mattermost, PostgreSQL, kube-prometheus-stack, Jenkins, Temporal, and NATS — looks tractable on paper. The charts are all upstream-maintained. The hardware is modest but adequate. The operational reality is that <strong>zero of the seven</strong> ran cleanly on out-of-the-box values. Every chart needed at least one customization to coexist with the others, and several needed substantial rewrites of the helm-values surface. This survey catalogs what those customizations are, why each was necessary, and what the common failure modes look like across the fleet.</p>