Group examples

Common configurations for each group type are provided below.

Contents

1. Example 1: Decoupling resources

Example 1: Decoupling resources

By default, DragonOps strikes a balance between separation of resources and cost-optimization. This means that multiple preprod environments are deployed to the same network and cluster. (See this for our default configuration and an explanation).

In this example, we will configure two groups instead, one called dev and one called stage. Each group will have its own network, cluster, and environment, completely separate from the other.

The dragonops-dev.yaml would look something like this:

dev_environment:
  type: environment
  name: dev
  cluster: dev_group.dev_cluster

dev_cluster:
  type: cluster
  name: dev
  network: dev_group.dev_network
  grafana:
    enabled: true
    subdomain: monitoring

dev_network:
  type: network
  name: dev
  cidr: 10.100.0.0/16

dev_group:
  account: "035473786027"
  region: us-east-1
  type: group
  name: dev

While the dragonops-stage.yml would look like this:

stage_environment:
  type: environment
  name: stage
  cluster: stage_group.stage_cluster

stage_cluster:
  type: cluster
  name: stage
  network: stage_group.stage_network
  grafana:
    enabled: true
    subdomain: monitoring

stage_network:
  type: network
  name: stage
  cidr: 10.100.0.0/16

stage_group:
  account: "035473786027"
  region: us-east-1
  type: group
  name: stage

With this configuration, applications deployed to the dev environment are completely siloed from applications deployed in the stage environment.