Before you apply
- Replace placeholder values in
deploy/k8s/secret.yaml - Or layer in your own secret management
Operate with confidence
Use Kubernetes or Helm when the cluster is already the job.
urgentry ships both raw Kubernetes manifests and a Helm chart for self-hosted mode. Use the raw manifests when you want the smallest explicit baseline. Use Helm when your cluster workflow already lives there.
Raw manifestsThe kustomize bundle lives under
deploy/k8s.Helm chartThe chart lives under
deploy/helm/urgentry.kind-friendly smokeThe local smoke path now loads images and temporary secrets for clean clusters.
Real cluster rulesFor production clusters, keep secret management in your normal workflow.
Raw manifests
Apply the kustomize bundle when you want the smallest explicit baseline.
kubectl apply -k deploy/k8s kubectl -n urgentry-system get pods
bash deploy/k8s/smoke.sh up
Helm
Use Helm when you already manage configuration and secrets that way.
helm upgrade --install urgentry deploy/helm/urgentry \ --set postgresql.password=changeme \ --set bootstrap.password=changeme
When to use Helm
- Your app configuration already lives in Kubernetes tooling
- Your secret flow already lives there too
What the local smoke path now does
- Builds and loads
urgentry:latestonkind-*contexts - Generates temporary dependency secrets
- Isolates temporary RWX PV paths by namespace and release
Next docs
Use the HA baseline to decide whether the topology is honest, or jump to maintenance mode if you are writing the operator runbook.