Expose chains metrics in openshift operator for monitoring

[sudhishmk]

Changes

• Exposing chains metrics for operator in OpenShift environment, fixes: ServiceMonitor for chains needed #1955
• Related to the PR

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Run make test lint before submitting a PR
• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices

See the contribution guide for more details.

Release Notes

NONE

[tekton-robot]

Hi @sudhishmk. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[khrm]

/ok-to-test

[khrm]

Please remove the draft from this.

[sudhishmk]

Please remove the draft from this.

Done

[savitaashture]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jkandasa

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 [jkandasa]

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

[jkandasa]

thanks @sudhishmk 🎉

[jkandasa]

/retest

[piyush-garg]

I am not sure if role and role binding is needed, is not only service monitor will do the job ?

[sudhishmk]

I am not sure if role and role binding is needed, is not only service monitor will do the job ?

did you mean that since we already have role and rolebinding defined for pipeline/ trigger monitoring service, new role and role binding is not needed?

[piyush-garg]

I am not sure if role and role binding is needed, is not only service monitor will do the job ?

did you mean that since we already have role and rolebinding defined for pipeline/ trigger monitoring service, new role and role binding is not needed?

Yes, we can even remove for triggers too, and keep single

[sudhishmk]

I am not sure if role and role binding is needed, is not only service monitor will do the job ?

did you mean that since we already have role and rolebinding defined for pipeline/ trigger monitoring service, new role and role binding is not needed?

Yes, we can even remove for triggers too, and keep single

Done.

[piyush-garg]

/lgtm