Provide a default configuration for integrating metrics from openshif…

[etsauer]

…t-monitoring

• I have read Pelorus Contributing guidelines

Linked Issues

Description

This change provides a default config for pulling in (federating) metrics from the openshift-monitoring instance that lives in the same cluster as Pelorus. This reduces the setup necessary to just a boolean value, rather than having to go grab passwords and store them.

Testing Instructions

[github-actions]

Test images available! 🧪🚀 To test operator with them, run

operator-sdk run bundle \
quay.io/pelorus/rc-pelorus-operator-bundle:vpr995-ca8070c \
--namespace test-pelorus-operator

To clean up environment afterwards, run

operator-sdk cleanup pelorus-operator --namespace test-pelorus-operator

[github-actions]

Test images available! 🧪🚀 To test operator with them, run

operator-sdk run bundle \
quay.io/pelorus/rc-pelorus-operator-bundle:vpr995-ef0f13a \
--namespace test-pelorus-operator

To clean up environment afterwards, run

operator-sdk cleanup pelorus-operator --namespace test-pelorus-operator

[github-actions]

Test images available! 🧪🚀 To test operator with them, run

operator-sdk run bundle \
quay.io/pelorus/rc-pelorus-operator-bundle:vpr995-b673edd \
--namespace test-pelorus-operator

To clean up environment afterwards, run

operator-sdk cleanup pelorus-operator --namespace test-pelorus-operator

[github-actions]

Test images available! 🧪🚀 To test operator with them, run

operator-sdk run bundle \
quay.io/pelorus/rc-pelorus-operator-bundle:vpr995-80a0699 \
--namespace test-pelorus-operator

To clean up environment afterwards, run

operator-sdk cleanup pelorus-operator --namespace test-pelorus-operator

[etsauer]

Any idea how to deal with this? Operator from the build above is failing with:

        constraints not satisfiable: subscription
        prometheus-beta-community-operators-openshift-marketplace requires
        @existing/test-pelorus-operator//prometheusoperator.0.56.3, subscription
        pelorus-operator-v0-0-7-pr995-b673edd-sub exists, subscription
        pelorus-operator-v0-0-7-pr995-b673edd-sub requires
        pelorus-operator-catalog/test-pelorus-operator/operator-sdk-run-bundle/pelorus-operator.v0.0.7-pr995-b673edd,
        bundle pelorus-operator.v0.0.7-pr995-b673edd requires an operator with
        package: prometheus and with version in range: 0.47.0,
        @existing/test-pelorus-operator//prometheusoperator.0.56.3 and
        community-operators/openshift-marketplace/beta/prometheusoperator.0.47.0
        originate from package prometheus, subscription
        prometheus-beta-community-operators-openshift-marketplace exists

[mateusoliveira43]

Any idea how to deal with this? Operator from the build above is failing with:

        constraints not satisfiable: subscription
        prometheus-beta-community-operators-openshift-marketplace requires
        @existing/test-pelorus-operator//prometheusoperator.0.56.3, subscription
        pelorus-operator-v0-0-7-pr995-b673edd-sub exists, subscription
        pelorus-operator-v0-0-7-pr995-b673edd-sub requires
        pelorus-operator-catalog/test-pelorus-operator/operator-sdk-run-bundle/pelorus-operator.v0.0.7-pr995-b673edd,
        bundle pelorus-operator.v0.0.7-pr995-b673edd requires an operator with
        package: prometheus and with version in range: 0.47.0,
        @existing/test-pelorus-operator//prometheusoperator.0.56.3 and
        community-operators/openshift-marketplace/beta/prometheusoperator.0.47.0
        originate from package prometheus, subscription
        prometheus-beta-community-operators-openshift-marketplace exists

I think you have an already installed Prometheus operator (this will happen to Grafana too). Run cleanup command and and uninstall the Prometheus/Operator, then run run bundle command again

[github-actions]

Test images available! 🧪🚀 To test operator with them, run

operator-sdk run bundle \
quay.io/pelorus/rc-pelorus-operator-bundle:vpr995-ff1b24d \
--namespace test-pelorus-operator

To clean up environment afterwards, run

operator-sdk cleanup pelorus-operator --namespace test-pelorus-operator

[github-actions]

Test images available! 🧪🚀 To test operator with them, run

operator-sdk run bundle \
quay.io/pelorus/rc-pelorus-operator-bundle:vpr995-048a221 \
--namespace test-pelorus-operator

To clean up environment afterwards, run

operator-sdk cleanup pelorus-operator --namespace test-pelorus-operator

[etsauer]

@mpryc @mateusoliveira43 updated to address your comments.

[github-actions]

Test images available! 🧪🚀 To test operator with them, run

operator-sdk run bundle \
quay.io/pelorus/rc-pelorus-operator-bundle:vpr995-25dd742 \
--namespace test-pelorus-operator

To clean up environment afterwards, run

operator-sdk cleanup pelorus-operator --namespace test-pelorus-operator

[etsauer]

/retest

[mpryc]

/lgtm

[mpryc]

@mateusoliveira43 could you please review?
@etsauer Should the title be without WIP and unhold or remove do-not-merge label?

[mateusoliveira43]

From my side, I still did not test it, I am missing testing instructions in the PR description (basically, an example yaml, but in this case, what does this change adds? how do I see them in OpenShift?)

[etsauer]

Instructions to test.

1. Install the latest PR build to your cluster
2. Apply the following Pelorus CR:

   kind: Pelorus
   apiVersion: charts.pelorus.dora-metrics.io/v1alpha1
   metadata:
     name: pelorus-sample
     namespace: test-pelorus-operator
   spec:
     federate_openshift_monitoring:
       enabled: true
       metrics_filter:
       # Just pull in one specific metric
       - 'kube_pod_container_info{}'
     exporters:
       global: {}
       instances: []

3. Go to the pelorus-prometheus web console, and run the following query: kube_pod_container_info{}. Should get multiple results back

[etsauer]

@mateusoliveira43 posted testing instructions above

[github-actions]

Test images available! 🧪🚀 To test operator with them, run

operator-sdk run bundle \
quay.io/pelorus/rc-pelorus-operator-bundle:vpr995-403bac6 \
--namespace test-pelorus-operator

To clean up environment afterwards, run

operator-sdk cleanup pelorus-operator --namespace test-pelorus-operator

[github-actions]

Test images available! 🧪🚀 To test operator with them, run

operator-sdk run bundle \
quay.io/pelorus/rc-pelorus-operator-bundle:vpr995-3a071de \
--namespace test-pelorus-operator

To clean up environment afterwards, run

operator-sdk cleanup pelorus-operator --namespace test-pelorus-operator

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mateusoliveira43

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mateusoliveira43]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mpryc]

/lgtm