Deploy with praisonai deploy helm
One command to helm upgrade –install either PraisonAI chart
Install or upgrade either PraisonAI Helm chart with one command that injects the right auth secrets for you.
Quick Start
- Create the auth Secret
Pre-create the token Secret out-of-band (GitOps-friendly).
bash kubectl create secret generic praisonai-api-auth \ --from-literal=PRAISONAI_API_TOKEN="$(openssl rand -hex 16)" - Install the chart
The wrapper runs
helm upgrade --installand wires the Secret automatically.bash praisonai deploy helm --chart agents-api
How It Works
The wrapper resolves the chart directory by alias, injects default --set secret references when you don’t, then shells out to Helm.
Command Options
| Flag | Default | Description |
|---|---|---|
--chart | (required) | Chart name: gateway or agents-api. |
--release / -r | praisonai | Helm release name. |
--namespace / -n | default | Kubernetes namespace. |
--chart-dir | (resolved) | Override the chart directory. |
--install / --no-install | --install | Toggle helm upgrade --install vs. plain upgrade. |
--json | False | Machine-readable output. |
The chart tree can be overridden with PRAISONAI_HELM_ROOT.
Auto-Injected Secrets
When you don’t supply the matching --set flags, the wrapper adds them for you.
--chart | Injected --set flags |
|---|---|
gateway | auth.existingSecret=praisonai-gateway-auth |
agents-api | auth.existingSecret=praisonai-api-auth and postgres.auth.existingSecret=praisonai-postgres-auth |
Worked Examples
Create the Secret first, then let the wrapper install the chart.
Gateway
kubectl create secret generic praisonai-gateway-auth \
--from-literal=GATEWAY_AUTH_TOKEN="$(openssl rand -hex 16)"
praisonai deploy helm --chart gatewayAgents API
kubectl create secret generic praisonai-api-auth \
--from-literal=PRAISONAI_API_TOKEN="$(openssl rand -hex 16)"
kubectl create secret generic praisonai-postgres-auth \
--from-literal=password="$(openssl rand -hex 16)"
praisonai deploy helm --chart agents-apiBest Practices
Pre-create Secrets, don't inline tokens
The wrapper references existingSecret names by default. Create those Secrets out-of-band so tokens never land in Git.
Use –no-install to guard existing releases
Pass --no-install to run a plain helm upgrade that fails if the release doesn’t already exist — useful in pipelines that shouldn’t create new releases.
Override the chart dir for local edits
Point --chart-dir at a working copy of the chart to test template changes before publishing.