# This deployment is applied separately from the main Helm chart - which
# sets up Drone, Gitea as a Drone source, and Prometheus and Grafana for
# monitoring and visualization - because it depends on Gitea being set up
# so that we can build and push an image to the Gitea registry.
#
# This could _probably_ be carried out fully automatically by having
# the deployment wait on the presence of the image in the Gitea registry
# (with an initContainer that waits on availability), but that seems like
# more complexity than is worth it for this proof-of-concept
apiVersion: apps/v1
kind: Deployment
metadata:
  name: drone-build-monitor-demo-monitor
  namespace: demo
spec:
  select:
    matchLabels:
      app: monitoring
  template:
    metadata:
      labels:
        app: monitoring
    spec:
      initContainers:
        - name: init
          image: "drone-build-monitor-demo-gitea-service.demo:3000/root/drone-monitor-init"
          imagePullPolicy: IfNotPresent
          command: ["/app/init.sh"]
          env:
            - name: PRIMARY_DRONE_USER_TOKEN
              valueFrom:
                secretKeyRef:
                  key: token
                  name: primary-drone-machine-user-secret
            - name: DRONE_URL
              value: "demo-drone.demo:8080"
      containers:
        - name: placeholder
          image: ubuntu