Skip to main content

☰ Deployments

Use this section to choose how you deploy Datalayer services on Kubernetes.

The deployment documentation is organized in five parts:

  1. Configuration: required environment variables and runtime settings shared by all deployment methods.
  2. Plane: direct service lifecycle commands (plane up, plane down) for day-0 and day-2 operations.
  3. Helm: chart-based deployment path when you want raw Helm workflows.
  4. Terraform: infrastructure + kubeadm bootstrap + generated service rollout scripts (AWS currently).
  5. GitHub Actions: CI/CD workflow built on Terraform artifacts and generated rollout scripts.

Which Deployment Path to Choose​

  1. Choose Configuration first.
  2. Choose Terraform if you want infrastructure provisioning and repeatable bootstrap automation.
  3. Choose Plane if your cluster is already provisioned and you want fast service operations.
  4. Choose Helm if your platform team standardizes on Helm-only workflows.
  5. Choose GitHub Actions for CI pipelines with plan/apply gates and staged rollout.
  1. Complete Configuration.
  2. Provision and bootstrap with Terraform.
  3. Deploy services using Plane rollout scripts or service-by-service commands.
  4. Add GitHub Actions for production CI/CD automation.

For a service-by-service deployment map, continue with Services.