Helm configuration

Chart.yaml

apiVersion: v2
name: drone-scubbo
description: A personalized Helm chart to deploy Drone to Kubernetes

# A chart can be either an 'application' or a 'library' chart.
#
# Application charts are a collection of templates that can be packaged into versioned archives
# to be deployed.
#
# Library charts provide useful utilities or functions for the chart developer. They're included as
# a dependency of application charts to inject those utilities and functions into the rendering
# pipeline. Library charts do not define any templates and therefore cannot be deployed.
type: application

# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/)
version: 0.1.0

# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application. Versions are not expected to
# follow Semantic Versioning. They should reflect the version the application is using.
# It is recommended to use it with quotes.
appVersion: "1.16.0"

dependencies:
  - name: drone
    repository: https://charts.drone.io
    version: "0.6.4"
    alias: drone-server
  - name: drone-runner-docker
    repository: https://charts.drone.io
    version: "0.6.1"
    alias: drone-runner

values.yaml

drone-server:
  env:
    DRONE_SERVER_HOST: drone.scubbo.org
    DRONE_SERVER_PROTO: https
    DRONE_RPC_SECRET: rpc-secret
    DRONE_GITEA_SERVER: https://gitea.scubbo.org
  extraSecretNamesForEnvFrom:
    - gitea-oauth-creds
  service:
    port: 3500
  persistentVolume:
    storageClass: longhorn

drone-runner:
  env:
    DRONE_RPC_SECRET: rpc-secret
    DRONE_RPC_HOST: drone-drone-server:3500 # This is the name of the service for the runner