feat: configure monitoring

[zachariahmiller]

Description

Enabled service and pod monitors in gitlab. For running on k3d-slim-dev in ci/local we dont have to update anything as the gitlab chart checks for the monitoring capabilities presence to deploy the service monitor templates.

Depends on uds-core 0.21.0.

Note: the pepr capability to mutate the service monitors but not pod monitors so we will need to request that feature or PR uds-core to add it. Adding the config for the pod monitor does no break anything.

As this wont get tested in CI in this repo (we should consider the "on-release" test that will exist soon to deploy a full cluster) I will provide visual proof in the comments. This requires no changes to the end user to enable.

Related Issue

Fixes #
116
Relates to #

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide Steps followed

[zachariahmiller]

[zachariahmiller]

This is ready for review but just want to throw this out there for discussion...

Example implementation using pepr 5 lines of yaml per monitor:

#monitor:
    - selector:
        app: gitaly
      targetPort: 9236
      portName: http-metrics
      description: Gitaly Metrics

Example implementation using the gitlab charts service monitors:

~5 lines in one file (there is a global disable for monitors and metrics true may be needed i dont recall so maybe more like 2 lines):

  gitaly:
    metrics:
      enabled: true
      serviceMonitor:
        enabled: true

and 8 in another (netpol isnt generated on mutation):

      - direction: Ingress
        remoteNamespace: monitoring
        remoteSelector:
          app: prometheus
        selector:
          app: gitaly
        port: 9236
        description: "Gitaly Service Monitor"

😭