Getting Started
Introduction
What OPSd is, who it is for, and why the output ownership model matters.
OPSd helps teams create a repeatable Kubernetes foundation and the platform configuration needed to start deploying applications.
The current primary path targets DigitalOcean Kubernetes. OPSd validates a manifest, resolves and pins provider modules, and renders infrastructure and selected Kubernetes components. Your team reviews and applies cloud changes, configures cluster access, and completes the initial GitOps handoff.
What OPSd is for
OPSd is designed for teams that want:
- a faster start than assembling a cluster foundation and platform integrations from scratch
- an isolated cloud project that makes OPSd-managed resources easier to identify
- a reviewable infrastructure and GitOps workflow that remains under the team’s control
Keep ownership and a clear exit path
Your team keeps the files OPSd uses and generates:
- the environment manifest
- the lock file with pinned module and chart inputs
- the rendered OpenTofu project
You can inspect and operate the rendered project without an OPSd runtime. When you need a portable handoff, opsd export exit-pack packages the rendered project and its handoff metadata into an archive. This keeps the work useful if your team changes its tools, workflow, or support model.
OPSd gives your team a faster, repeatable start while leaving the resulting infrastructure under your control.
Start from a Kubernetes foundation
The current primary blueprint is kubernetes-foundation for DigitalOcean. It provisions a DOKS cluster, a default node pool, a VPC, and a DigitalOcean project. The CLI can also render selected platform components such as Argo CD, DOKS Gateway API resources, ExternalDNS, cert-manager, and External Secrets Operator when their manifest conditions are met.
Use the manifest to describe the environment
The manifest records the environment and selected platform components. Module versions and chart artifacts are pinned in opsd.lock.yaml so future renders can use the same inputs.
Keep the operator in the loop
Terraform or OpenTofu applies the cloud foundation after a human reviews the plan. Argo CD is installed with private access; an operator connects through Kubernetes port forwarding and completes the first GitOps setup. DNS tokens and other credentials are supplied separately.
Understand the current boundary
Monitoring and turnkey application CI integration are future platform work. The DigitalOcean Secrets Manager webhook example for External Secrets is experimental and is not qualified for production use.
Follow How It Works for the guided setup, or review Supported Paths for current capabilities and manual handoffs.
Who OPSd is for
OPSd is a good fit for teams that:
- want to manage their own infrastructure and need a prepared Kubernetes base
- want to review and control infrastructure changes rather than delegate cloud access to a hosted control plane
- want to connect their applications through a client-owned GitOps repository
OPSd is designed for your organization to operate the resulting infrastructure itself. If you are short on time or prefer to hand off operations, you can get hourly OPSd support or ask ZeroDowntime to implement or take over an agreed scope. Continue with the Installation guide, then follow the Kubernetes deployment walkthrough after the Quickstart.