usage of metrics-reader ClusterRole

[mohammadne]

Type of question

Open question

Question

What did you do?

I want to know what is the usage of metrics-reader ClusterRole in rbac, because I don't see any ClusterRoleBinding defined for it and it's always unusable.

What did you expect to see?

I want to delete metrics-reader ClusterRole or define a ClusterRoleBinding and subject it to the ServiceAccount used by the Deployment

Environment

Operator type: /language go

Kubernetes cluster type: k8s cluster deployed via kubespray

$ operator-sdk version v1.31.0

$ go version (if language is Go) 1.19.11

$ kubectl version 1.27

[varshaprasad96]

This cluster role is scaffolded to allow the prometheus server to scrape metrics. The creation of cluster role binding is left to the user, depending on the namespace where prometheus is available.

More details on its use and on how to create the cluster role binding for the cluster role are available here; https://book.kubebuilder.io/reference/metrics.html?highlight=prometheus#exporting-metrics-for-prometheus

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.