Enables automatic prometheus scrapping for controller's service

[jpmcb]

- Adds prometheues config map to the brupop namespace

Signed-off-by: John McBride <jpmmcb@amazon.com>

ssue number:

Closes #159

Description of changes:

This commit adds the

  annotations:
    prometheus.io/port: "8080"
    prometheus.io/scrape: "true"

to the controller service (so that prometheus may automatically start scraping metrics when deployed).

This also adds a missing namespace delimiter for the prometheus-config ConfigMap. Otherwise, I would get an error that the configmap could not be found

From the kubernetes docs:

You can write a Pod spec that refers to a ConfigMap and configures the container(s) in that Pod based on the data in the ConfigMap. The Pod and the ConfigMap must be in the same namespace.

Ref: https://kubernetes.io/docs/concepts/configuration/configmap/#configmaps-and-pods

Testing done:

Deployed cert-manager, the modified bottlerocket-update-operator.yaml, and the modified yamlgen/telemetry/prometheus-resources.yaml to a bottlerocket based cluster.

I see that automatically Prometheus starts scraping the metrics:

$ curl http://localhost:9090/api/v1/label/__name__/values
{"status":"success","data":["brupop_hosts_state","brupop_hosts_version" ... }

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

[stmcginnis]

Looks reasonable.

[gthao313]

I tested it and worked on my side. Nice work!