[feature] Helm charts for Kubernetes deployment

[ClaireGz]

Problem

nao currently lacks an official Helm chart for Kubernetes deployment. Self-hosted users on K8s have to roll their own packaging, which makes installs and upgrades harder than necessary and prevents unified configuration across deployments.

Expected behavior

Publish an official Helm chart that:

• Packages all nao components for a standard K8s install
• Exposes a unified config surface (values.yaml) covering the variables users currently set across multiple files
• Supports upgrades cleanly
• Follows a model similar to Airbyte's Helm approach (referenced as a good pattern by enterprise self-hosters)

Impact

Reported by an enterprise self-hosting customer: nearly all of their nao deployments run on Kubernetes. Without Helm, every new install is bespoke. Several other enterprise prospects in the pipeline are also K8s-first and would benefit from this.

[harshil4076]

@ClaireGz I can take on to this one if no one is working on it.
I have built helm chars for k8s deployment previously.

[mfournioux]

Hi @ClaireGz , I've built a Helm chart that covers this — it packages all nao components for a standard K8s install with a unified values.yaml, supports clean upgrades/rollbacks via Helm's built-in revision history, and includes autoscaling (HPA) and PodDisruptionBudget for production use.

It supports all three nao context modes (local PVC, git-based, and API-driven project deployment), plus optional bundled PostgreSQL or an external DB connection.

I've opened a PR here: #1100

It was auto-closed pending maintainer approval — happy to iterate on it based on feedback if this direction looks good for the project.