When the contour is a Kubernetes cluster, the vendor applies the charts and values — there is no public Helm chart and no helm install from a public git clone.
Namespace, release name, and image pull secrets are defined in the delivery. Use those names; do not invent a public chart path.
What the vendor installs
Typical objects:
- Application Deployment and Service (HTTP)
- Realtime Deployment and Service (WebSocket)
- PostgreSQL (in-cluster) or a pointer at a managed database
- Ingress / Gateway with TLS for
pailot.yourdomain.com - Secrets for
BETTER_AUTH_SECRET,ENCRYPTION_KEY,INTERNAL_API_SECRET, and provider keys
Values the customer must provide
| Item | Example |
|---|---|
| Public URL | https://pailot.yourdomain.com |
| Ingress host | pailot.yourdomain.com |
| Image pull | Private registry credentials from the delivery |
| Database | In-cluster PVC size, or host / user / database for an external Postgres with pgvector |
External database example shape (names come from the delivery):
postgresql:
enabled: false
externalDatabase:
enabled: true
host: "your-db-host"
port: 5432
username: "postgres"
password: "your-password"
database: "pailot"
sslMode: "require"Day-2 commands
Use the namespace and labels from the runbook:
kubectl -n <namespace> get pods
kubectl -n <namespace> logs -l app.kubernetes.io/component=app --tail=100
kubectl -n <namespace> port-forward deploy/<app-deploy> 3000:3000Upgrades and rollbacks are a vendor change (new images + migrate job). Do not helm upgrade a chart that was not part of the delivery.