# Default values for drone-build-status-monitor.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

replicaCount: 1

image:
  repository: nginx
  pullPolicy: IfNotPresent
  # Overrides the image tag whose default is the chart appVersion.
  tag: ""

imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""

serviceAccount:
  # Specifies whether a service account should be created
  create: true
  # Annotations to add to the service account
  annotations: {}
  # The name of the service account to use.
  # If not set and create is true, a name is generated using the fullname template
  name: ""

podAnnotations: {}

podSecurityContext: {}
  # fsGroup: 2000

securityContext: {}
  # capabilities:
  #   drop:
  #   - ALL
  # readOnlyRootFilesystem: true
  # runAsNonRoot: true
  # runAsUser: 1000

service:
  type: ClusterIP
  port: 80

ingress:
  enabled: false
  className: ""
  annotations: {}
    # kubernetes.io/ingress.class: nginx
    # kubernetes.io/tls-acme: "true"
  hosts:
    - host: chart-example.local
      paths:
        - path: /
          pathType: ImplementationSpecific
  tls: []
  #  - secretName: chart-example-tls
  #    hosts:
  #      - chart-example.local

resources: {}
  # We usually recommend not to specify default resources and to leave this as a conscious
  # choice for the user. This also increases chances charts run on environments with little
  # resources, such as Minikube. If you do want to specify resources, uncomment the following
  # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
  # limits:
  #   cpu: 100m
  #   memory: 128Mi
  # requests:
  #   cpu: 100m
  #   memory: 128Mi

autoscaling:
  enabled: false
  minReplicas: 1
  maxReplicas: 100
  targetCPUUtilizationPercentage: 80
  # targetMemoryUtilizationPercentage: 80

nodeSelector: {}

tolerations: []

affinity: {}

# Everything below here was hand-created

# Set these if you want to use an existing secret for the Drone
# tokens (otherwise, fresh ones will be created if necessary)
#
# Note the required format of the secret pointed to by
# `primaryDroneMachineUserToken` - it must have two entries:
# * `DRONE_USER_CREATE=username:root,admin:true,machine:true,token:<token>`
# * `token=<token>`
#
# For explanation why, see https://community.harness.io/t/is-it-possible-to-create-a-new-user-from-a-command-on-the-image-itself/12899/4
primaryDroneMachineUserSecret: ""

# Subchart values
kube-prometheus-stack:
  grafana:
    enabled: false

# TODO - fill out appropriate values here
drone:
  extraSecretNamesForEnvFrom:
    - primary-drone-machine-user-secret
  env:
    DRONE_SERVER_HOST: drone-monitoring-demo.local
    DRONE_RPC_SECRET: hard-coding-is-very-bad-do-not-do-this-in-production
    DRONE_GITEA_SERVER: drone-build-monitor-demo-gitea-service.demo