Skip to content

Deploying to DigitalOcean

Cdev uses stack templates to generate projects in a desired cloud. This section describes the steps necessary to start working with cdev in DigitalOcean cloud using DO-k8s stack template.

Prerequisites to use DO-k8s stack template

  1. Terraform version 13+.

  2. DigitalOcean account.

  3. doctl installed.

  4. Cdev installed.


Create an access token for a user.


Make sure to grant the user with administrative permissions.

For details on using DO spaces bucket as a backend, see here.

Configure access to DigitalOcean

  1. Install doctl. For more information, see the official documentation.

    cd ~
    tar xf ~/doctl-1.57.0-linux-amd64.tar.gz
    sudo mv ~/doctl /usr/local/bin
  2. Export your DIGITALOCEAN_TOKEN, for details see here.

  3. Export SPACES_ACCESS_KEY_ID and SPACES_SECRET_ACCESS_KEY environment variables, for details see here.

    export SPACES_SECRET_ACCESS_KEY="dSUGdbJqa6xwJ6Fo8qV2DSksdjh..."
    export SPACES_SECRET_ACCESS_KEY="TEaKjdj8DSaJl7EnOdsa..."
  4. Create a spaces bucket for Terraform states in the chosen region (in the example we used the 'cdev-data' bucket name).

  5. Create a domain in DigitalOcean domains service.


In the project generated by default we used '' zone as an example. Please make sure to change it.


DO-k8s is a cdev stack template that creates and provisions Kubernetes clusters in the DigitalOcean cloud.

DO-k8s starting guide

  1. Configure access to DigitalOcean and export required variables.

  2. Create locally a project directory, cd into it and execute the command:

      cdev project create


    The stack template's repo could contain several options for project generation. To list available generators, use --list-templates option:

    cdev project create --list-templates

    Then you can specify which generator to use, for example:

    cdev project create minimal


    If you leave it unspecified, cdev will generate a default project for you. You can also opt for an interactive mode with the extended menu:

    cdev project create --interactive
  3. Edit variables in the example's files, if necessary:

    • project.yaml - main project config. Sets common global variables for current project such as organization, region, state bucket name etc. See project configuration docs.

    • backend.yaml - configures backend for cdev states (including Terraform states). Uses variables from project.yaml. See backend docs.

    • infra.yaml - describes stack configuration. See stack docs.

  4. Run cdev plan to build the project. In the output you will see an infrastructure that is going to be created after running cdev apply.


    Prior to running cdev apply make sure to look through the infra.yaml file and replace the commented fields with real values. In case you would like to use existing VPC and subnets, uncomment preset options and set correct VPC ID and subnets' IDs. If you leave them as is, cdev will have VPC and subnets created for you.

  5. Run cdev apply


    We highly recommend to run cdev apply in a debug mode so that you could see cdev logging in the output: cdev apply -l debug

  6. After cdev apply is successfully executed, in the output you will see the ArgoCD URL of your cluster. Sign in to the console to check whether ArgoCD is up and running and the stack template has been deployed correctly. To sign in, use the "admin" login and the bcrypted password that you have generated for the infra.yaml.

  7. Displayed in the output will be also a command on how to get kubeconfig and connect to your Kubernetes cluster.

  8. Destroy the cluster and all created resources with the command cdev destroy

Resources to be created

  • (optional, if vpc_id is not set) VPC for Kubernetes cluster
  • DO Kubernetes cluster with addons:
    • cert-manager
    • argocd