Skip to content

Getting started on DigitalOcean

Deploying to DigitalOcean

  1. Create a separate repository for the infrastructure code that will be managed by in GitHub. This repo will host code for your clusters, deployments, applications and other resources. Clone the repo locally:

    git clone

Next steps should be done inside that repo.

  1. Login to your DO account. You can create a default VPC inside your account: Manage->Networking->VPC-Create VPC Network.

  2. Next, you need to generate a DO API token and DO Spaces keys. To generate the API token, see the DO documentation. The token should like:

    DIGITALOCEAN_TOKEN: "83e209a810b6c1da8919fe7265b9493992929b9221444449"

    To generate the DO Spaces secrets, see the DO documentation.

    The resulting key and secret should look like:

    SPACES_SECRET_ACCESS_KEY: "njVtezJ7t2ce1nlohIFwoPHHF333mmcc2"

    Add the token and Spaces keys to your repo secrets or env variables. In GitHub: Settings → Secrets, the path should look like:

  3. In your repo, create a Github workflow file: .github/workflows/main.yml and example manifest: with the cluster definition.

    Or download example files to your local repo clone using the next commands:

    # Sample with DO Managed Kubernetes Cluster
    export RELEASE=v0.3.3
    mkdir -p .github/workflows/ && wget -O .github/workflows/main.yml "${RELEASE}/.github/workflows/digitalocean.yml"
    mkdir -p && wget -O "${RELEASE}/"
  4. In the cluster manifest ( you can set your own Domain Zone. If you don't have any hosted public zone you can set just domain: and we will create it for you. Or you can create it manually and add to your account with instructions from DO website.

  5. You can change all other parameters or leave default values in the cluster manifest. Leave the Github workflow file .github/workflows/main.yml as is.

  6. Copy sample ArgoCD Applications from /kubernetes/apps/samples and Helm chart samples from /kubernetes/charts/wordpress to the same paths into your repo.

    Or download application samples directly to local repo clone with the commands:

    export RELEASE=v0.3.3
    # Create directory and place ArgoCD applications inside
    mkdir -p kubernetes/apps/samples && wget -O kubernetes/apps/samples/helm-all-in-app.yaml "${RELEASE}/kubernetes/apps/samples/helm-all-in-app.yaml"
    wget -O kubernetes/apps/samples/helm-dependency.yaml "${RELEASE}/kubernetes/apps/samples/helm-dependency.yaml"
    wget -O kubernetes/apps/samples/raw-manifest.yaml "${RELEASE}/kubernetes/apps/samples/raw-manifest.yaml"
    # Download sample chart which with own values.yaml
    mkdir -p kubernetes/charts/wordpress && wget -O kubernetes/charts/wordpress/Chart.yaml "${RELEASE}/kubernetes/charts/wordpress/Chart.yaml"
    wget -O kubernetes/charts/wordpress/requirements.yaml "${RELEASE}/kubernetes/charts/wordpress/requirements.yaml"
    wget -O kubernetes/charts/wordpress/values.yaml "${RELEASE}/kubernetes/charts/wordpress/values.yaml"

    Define path to ArgoCD apps in the cluster manifest:

        - /kubernetes/apps/samples
  7. Commit and Push files to your repo.

  8. Set the cluster to installed: true, commit, push and follow the Github Action execution status, the path should look like In the GitHub action output you'll receive access instructions to your cluster and services:

  9. Voilà! You receive GitOps managed infrastructure in code. So now you can deploy applications, create more clusters, integrate with CI systems, experiment with the new features and everything else from Git without leaving your IDE.