Choose a deployment
| Concern | Standalone | Kubernetes with Helm |
|---|---|---|
| Best fit | Demo, evaluation, one small SVM pair | Production and larger fleets |
| Runtime | Docker Compose | Kubernetes 1.25+ and Helm 3.8+ |
| Identity and secrets | Bundled dev-mode Keycloak and Vault | External OIDC and Vault |
| Database | Bundled PostgreSQL volume | External PostgreSQL recommended; bundled optional |
| Availability | One application container | One or more app replicas; reconcile stays single-writer |
| Exposure | Local HTTP on host.docker.internal | Your Ingress, Gateway API route, or port-forward |
Deployment assets are published at github.com/saragihruben/donkeyfleet. The standalone stack is the fastest evaluation path, but its fixed development credentials and in-memory Vault are not a hardened control plane.
Whichever deployment you choose:
- Start with effective dry-run enabled.
- Use read-only credentials for source-role clusters.
- Store credentials outside values files and source control.
- Back up PostgreSQL; it holds approvals, provisioning checkpoints, job UUIDs, and audit state.
- Verify OIDC, Vault, PostgreSQL, and every ONTAP endpoint from each application node.
Continue with the standalone quickstart or Kubernetes quickstart.