Drone CI stack for Kubernetes

Module deploys Drone CI stack helm charts set. Possible deployment setups:

deploy Drone Server and Runner locally in cluster
deploy only Drone Server exposed externally for Drone Runner(s) to connect to
deploy only Drone Runner with connection to an externally exposed remote Drone server

NOTE: For the Drone Server deployment the PostgreSQL or MySQL database instance must be created already.

NOTE: For the dashboard UI Drone Server and Drone Runner expect Nginx as Ingress class as dependency for this module.

Drone Runner Labeling Notes

A note for DRONE_RUNNER_LABELS selectors with node keyword. A pipeline is not routed to a runner unless it matches all runner labels. If the pipeline only defines and matches a subset of runner labels it will not be routed to the runner. It means that if a runner has several labels, then you must provide all of them in node section. You can specify multiple runners by providing all labels of each runner in node list. Although, only the drone runner which was attached the last will execute a pipeline if several node labels are set within the pipeline. Don't specify node section at all if the pipeline should run on any runner (or on runners without labels).

Examples: you have runner with no labels, runner2 with label runner2:2 and runner3 with labels runner3:3,runner-arch:linux. if you skip node section, then pipeline will be executed in runner runner. If you set:

 yamlnode:
  runner2: 2

then a pipeline will be executed on runner2. If you set:

 yamlnode:
  ## Runner2 label
  runner2: 2
  ## Runner3 labels
  runner3: 3
  runner-arch: linux

then a pipeline will be executed on a runner which was attached last: either runner2 or runner3. If you set:

 yamlnode:
  ## Only one of two runner3 labels
  runner3: 3

then Drone Server will not find any suitable runners at all since the second runner3 labels are missing.

$850

BUY

License

Once you have a Corewide Solutions Portal account, this one-time action will use your browser session to retrieve credentials:

 shellterraform login solutions.corewide.com

Provision instructions

Initialize mandatory providers:

Copy and paste into your Terraform configuration and insert the variables:

 hclmodule "tf_k8s_drone_ci" {
  source  = "solutions.corewide.com/kubernetes/tf-k8s-drone-ci/helm"
  version = "~> 2.0.2"

  # specify module inputs here or try one of the examples below
  ...
}

Initialize the setup:

 shellterraform init

Define update strategy

Corewide DevOps team strictly follows Semantic Versioning Specification to provide our clients with products that have predictable upgrades between versions. We recommend pinning patch versions of our modules using pessimistic constraint operator (~>) to prevent breaking changes during upgrades.

To get new features during the upgrades (without breaking compatibility), use ~> 2.0 and run terraform init -upgrade

For the safest setup, use strict pinning with version = "2.0.2"

v2.0.2 released 2 years, 1 month ago

New version approx. every 9 weeks

Upgrade Notes

Changelog

From `v1.x` to `v2.x`

Now all kubernetes provider resources use versioned resources. According to kubernetes provider's suggestions the simplest, non-destructive way to do this is to remove the old resource from state and import this resource as a version one, like so:

 bash# If Kubernetes namespace was managed by the module, it must be re-imported
terraform state rm module.drone_ci.kubernetes_namespace.namespace[0]
terraform import module.drone_ci.kubernetes_namespace_v1.namespace[0] drone
# If there were namespaces that Drone runner needs to access, their settings must be re-imported
terraform state rm module.drone_ci.kubernetes_role.drone_runner["backend"] module.drone_ci.kubernetes_role_binding.drone_runner["backend"]
terraform import module.drone_ci.kubernetes_role_v1.drone_runner["backend"] drone-runner-backend
terraform import module.drone_ci.kubernetes_role_binding_v1.drone_runner["backend"] drone-runner-backend

From `v2.x` to `v3.x`

Now Drone runner uses deployment of Docker type. All the pipelines processed by a managed Drone runner must be updated to use docker type:

 yml---
kind: pipeline
type: docker

To pull the Docker images from private registries, a Drone secret with credentials to the private container registry must be created and referenced in pipelines:

 ymlsteps:
- name: build
  image: registry.internal.company.com/golang:1.12
  commands:
  - go build
  - go test

image_pull_secrets:
- dockerconfig

For K8S management (e.g. by means of kubectl or/and helm tools) K8S configuration files must be provided in the pipeline steps. For example, a step can be added in the pipeline that will retrieve and save a K8S configuration file in the default Drone workspace directory (which content will be available between all of the steps within the running pipeline) and reference this saved file in kubectl or/and helm commands of the next steps in the same pipeline.

WARNING: Do not roll out Drone Runner on the node managed in the subnet with 172.17.0.0/16 address pool, because it will overlap with the default docker0 network.

drone_rpc_secret output is defined as a string instead of a list with one element if Drone Server deployment is enabled, and its references should be updated accordingly:

 hclmodule.drone_ci.drone_rpc_secret[0]  ==>  module.drone_ci.drone_rpc_secret

Deploy locally Drone Server and Runner without web UI:

 hclmodule "drone_ci" {
  source  = "solutions.corewide.com/kubernetes/tf-k8s-drone-ci/helm"
  version = "~> 2.0"

  drone_server = {
    enabled          = true
    ingress_host     = "drone.host.com"
    drone_admin_user = "admin"

    db_connection_settings = {
      db_host     = "db-host.com"
      db_login    = "db-login"
      db_name     = "db-name"
      db_password = "db-password"
    }

    scm_settings = {
      type          = "GitHub"
      client_id     = "client_id"
      client_secret = "client_secret"
    }
  }

  drone_runner = {
    count = 1
  }
}

Deploy Drone Server and Runner with access to the "backend" namespace in the cluster it runs in:

 hclmodule "drone_ci" {
  source  = "solutions.corewide.com/kubernetes/tf-k8s-drone-ci/helm"
  version = "~> 2.0"

  drone_server = {
    enabled          = true
    ingress_host     = "drone.host.com"
    drone_admin_user = "admin"

    db_connection_settings = {
      db_host     = "db-host.com"
      db_login    = "db-login"
      db_name     = "db-name"
      db_password = "db-password"
    }

    scm_settings = {
      type          = "GitHub"
      client_id     = "client_id"
      client_secret = "client_secret"
    }
  }

  drone_runner = {
    count         = 1
    cd_namespaces = ["backend"]
  }
}

Deploy only Drone Runner with an enabled web UI and custom label:

 hclmodule "drone_ci" {
  source  = "solutions.corewide.com/kubernetes/tf-k8s-drone-ci/helm"
  version = "~> 2.0"

  drone_server = {
    enabled = false
  }

  drone_runner = {
    count             = 1
    server_address    = "drone.host.com"
    server_token      = "token"
    dashboard_enabled = true
    dashboard_host    = "drone-runner.host.com"
    labels            = ["env:dev"]
  }
}

Deploy only Drone Server and set a variable for secrets encryption:

 hclmodule "drone_ci" {
  source  = "solutions.corewide.com/kubernetes/tf-k8s-drone-ci/helm"
  version = "~> 2.0"

  drone_server = {
    enabled          = true
    drone_admin_user = "admin"
    ingress_host     = "drone.host.com"

    db_connection_settings = {
      db_host     = "db-host.com"
      db_login    = "db-login"
      db_name     = "db-name"
      db_password = "db-password"
    }

    scm_settings = {
      type          = "GitHub"
      client_id     = "client_id"
      client_secret = "client_secret"
    }

    custom_values = {
      env.DRONE_DATABASE_SECRET = "7c229228a77d2cbddaa61ddc78d45e"
    }
  }

  drone_runner = {
    count = 0
  }
}

Variable	Description	Type	Default	Required	Sensitive
`drone_runner`	Set of parameters for the Drone Runner	`object`		yes	no
`drone_server`	Set of parameters for the Drone Server	`object`		yes	no
`name_prefix`	Naming prefix for all the resources created by the module	`string`		yes	no
`create_namespace`	Indicates creation of dedicated namespace for Drone CI deployment	`bool`	`true`	no	no
`drone_runner.app_version`	Version of Drone Rrunner image to use	`string`	`1.0.0-rc.3`	no	no
`drone_runner.cd_namespaces`	A list of Namespaces in K8S cluster that Drone Runner should be able to access. Only for access within the same cluster that hosts Runner. If only `"all"` provided in the list - it is treated as allowing `edit` permissions to the whole cluster	`list(string)`	`[]`	no	no
`drone_runner.chart_version`	Version of Drone Runner Helm chart to use	`string`	`0.1.8`	no	no
`drone_runner.concurrent_jobs`	Number of concurrent jobs Drone Runner will handle	`number`	`2`	no	no
`drone_runner.count`	How many runner replicas should be installed (`0` to disable runner installation)	`number`		yes	no
`drone_runner.custom_values`	Custom Helm chart values in key value format	`map(string)`	`{}`	no	no
`drone_runner.dashboard_auth_credentials`	Set of Drone Runner dashboard access credentials	`object`		no	no
`drone_runner.dashboard_auth_credentials.password`	Drone Runner dashboard password	`string`		no	no
`drone_runner.dashboard_auth_credentials.user`	Drone Runner dashboard username	`string`	`drone`	no	no
`drone_runner.dashboard_enabled`	Whether Drone Runner dashboard should be enabled	`bool`	`false`	no	no
`drone_runner.dashboard_host`	Valid domain name to expose web dashboard at (required only in case if Drone Runner dashboard is enabled)	`string`		no	no
`drone_runner.labels`	A list of runner labels to be attached. Each list element should have `key:value` format. Example: `["runner-name:jack", "runner-name:josh"]`	`list(string)`	`[]`	no	no
`drone_runner.node_selector`	Selector of node group to place Drone Runner in	`map(string)`	`{}`	no	no
`drone_runner.server_address`	Address of Drone Server (not required for local Drone Server and mandatory for creating only a runner with connection to an externally exposed remote Drone Server)	`string`		no	no
`drone_runner.server_token`	RPC token to connect to a remote Drone CI Server (not required for local Drone Server and mandatory for creating only a runner with connection to an externally exposed remote Drone Server)	`string`		no	no
`drone_server.app_version`	Version of Drone Server image to use	`string`	`2.12.0`	no	no
`drone_server.chart_version`	Version of Drone Server Helm chart to use	`string`	`0.6.4`	no	no
`drone_server.custom_values`	Custom Helm chart values in key value format	`map(string)`	`{}`	no	no
`drone_server.db_connection_settings`	Set of connection parameters of Drone database	`object`		no	no
`drone_server.db_connection_settings.db_driver`	Defines database engine type (`PostgreSQL` and `MySQL` are allowed)	`string`	`postgresql`	no	no
`drone_server.db_connection_settings.db_host`	Database connection endpoint	`string`		no	no
`drone_server.db_connection_settings.db_login`	Database instance login	`string`		no	no
`drone_server.db_connection_settings.db_name`	Database name	`string`		no	no
`drone_server.db_connection_settings.db_password`	Database instance password	`string`		no	no
`drone_server.db_connection_settings.db_port`	Database instance port	`number`		no	no
`drone_server.drone_admin_user`	The name of Drone Server admin user	`string`		no	no
`drone_server.enabled`	Whether Drone Server should be installed	`bool`		yes	no
`drone_server.ingress_host`	Valid domain name for Drone web UI	`string`		no	no
`drone_server.node_selector`	Selector of node group to place Drone Server in	`map(string)`	`{}`	no	no
`drone_server.scm_settings`	Set of parameters to manage connection of Drone to Source Control Management system	`object`		no	no
`drone_server.scm_settings.client_id`	SCM oauth client ID	`string`		no	no
`drone_server.scm_settings.client_secret`	SCM oauth client secret	`string`		no	no
`drone_server.scm_settings.host`	SCM server URL (can be mandatory for some compatible SCM types)	`string`		no	no
`drone_server.scm_settings.type`	SCM system type (Github, Gitlab, Gogs, Gitea, Bitbucket, Gitee)	`string`		no	no
`ingress_cert_issuer`	Ingress Nginx TLS certificate issuer	`string`	`letsencrypt`	no	no
`logs_debug_mode`	Whether logging mode should be set to Debug	`bool`	`false`	no	no
`namespace`	The namespace to install the Drone into	`string`	`drone`	no	no

Output	Description	Type	Sensitive
`drone_rpc_secret`	A shared secret to authenticate communication between runners and Drone server	`list(attribute)`	yes
`runner_dashboard_credentials`	Access credentials for the Drone runner UI	`map`	yes