Hermes Helm chart shared

A community developer published an unofficial Helm chart that packages Nous Research’s Hermes Agent for Kubernetes clusters, with built-in guardrails for persistent state. (github.com) Helm is a packaging system for Kubernetes, the software layer many companies use to deploy apps across clusters of servers. The new chart says its default mode renders Hermes deployments, storage, secrets, services, ingress, Istio resources, and other support objects directly from one install. (github.com) Hermes Agent is an open-source agent from Nous Research that runs on a server, keeps memory across sessions, and can expose a gateway for messaging and other interfaces. Nous Research’s public repository shows the project was active this week, and its latest v0.8.0 release was published on April 8, 2026. (github.com 1) (github.com 2) The chart’s main safety feature is simple: when persistent storage is turned on, it enforces one replica and a “Recreate” rollout so two Hermes pods do not write to the same home directory at once. The README ties that rule to `HERMES_HOME`, where Hermes stores mutable data. (github.com) That matters in Kubernetes because the platform is built to restart, reschedule, and scale containers automatically. For software that keeps changing local state, those defaults can corrupt data unless operators pin it to a single writer. (github.com) The chart also targets service-mesh setups, where a control layer manages traffic, identity, and policy between apps. Its README lists optional Istio `VirtualService` support alongside ingress, role-based access control, network policies, and pod disruption budgets. (github.com 1) (github.com 2) For secrets, the chart can create Kubernetes Secret and ConfigMap objects itself or point to ones managed elsewhere with `existingSecret` and `existingConfigMap`. That fits the common pattern used by External Secrets Operator, which pulls credentials from systems such as Amazon Web Services Secrets Manager and injects them into Kubernetes Secrets. (github.com 1) (github.com 2) The multi-tenant piece is aimed at shared clusters, where one platform team runs infrastructure for many internal users or customers. The chart recommends one Helm release per tenant in direct mode, while External Secrets Operator’s own documentation warns that shared secret stores can expose too much unless access is narrowed by namespace or key prefix. (github.com) (external-secrets.io) The repository also says the chart is unofficial and maintained independently from the upstream Hermes project. That leaves platform teams with a clearer tradeoff: they can use a Kubernetes-native packaging layer for Hermes now, but they are relying on a community integration rather than a chart shipped by Nous Research itself. (github.com)