[receiver/k8sclusterreceiver] add HierarchicalResourceQuota

[hiwayama]

Description:

Add hnc.x-k8s.io/v1alpha2 HierarchicalResourceQuota as a target for metrics collection (Optional)
https://github.com/kubernetes-sigs/hierarchical-namespaces

A custom controller of HierarchicalResourceQuota has no imformer.
So, I use dynamic informers to collect these metrics.

Link to tracking Issue:
#29555

Testing:
I tested to collect hrq metrics with k8sclusterreceiver and debugexporter in a k8s cluster which is installed HierarchicalResourceQuota
ut: Add test case to collect metrics from hrq in receiver/k8sclusterreceiver/receiver_test.go#TestReceiver

Documentation:
I added some options for hrq.
The default value of hrq sets false.

[hiwayama]

Please code review.

I'm sorry. The label pkg/stanza was given in error. Please remove that label.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[povilasv]

I think we are also missing some docs around how to use this / RBAC? :)

Sorry for delayed reviews. I will try to also build this and test it early next week.

[hiwayama]

Thank you for your reponse.

I think we are also missing some docs around how to use this / RBAC? :)

I missed writing docs about how to use and RBAC.
I'll write them.

[hiwayama]

@povilasv

I think we are also missing some docs around how to use this / RBAC? :)

I added some descriptions about RBAC bfb5b3b

If you would like another method please let me know.
For example, should it be a separate item like descrptions about OpenShift?

[povilasv]

Looks ok to me. @TylerHelmuth / @dmitryax would be great if you could take a look

[TylerHelmuth]

LGTM. @dmitryax @jinja2 would appreciate your review

[jinja2]

Suggested change

	k8s.hierarchical_resource_quota.hard_limit:
	k8s.hierarchicalresourcequota.limit:

This will keep the metric names in-line with the attr names which do not have underscore. Are we adding hard_limit explicitly cause there is another type of limit with these (e.g. soft_limit)?

[hiwayama]

I refer to the following lines.
Should I change that setting to 'limit'?

opentelemetry-collector-contrib/receiver/k8sclusterreceiver/metadata.yaml

Lines 418 to 433 in 6a0b248

	k8s.resource_quota.hard_limit:
	enabled: true
	description: The upper limit for a particular resource in a specific namespace. Will only be sent if a quota is specified. CPU requests/limits will be sent as millicores
	unit: "{resource}"
	gauge:
	value_type: int
	attributes:
	- resource
	k8s.resource_quota.used:
	enabled: true
	description: The usage for a particular resource in a specific namespace. Will only be sent if a quota is specified. CPU requests/limits will be sent as millicores
	unit: "{resource}"
	gauge:
	value_type: int
	attributes:
	- resource

[povilasv]

There is an interesting issue about building a way for users to monitor custom CRDS without us adding new dependencies in k8sclusterreceiver - #30655

Maybe we should pursue this instead? 🤔

[hiwayama]

Thank you for sharing the issue.
It is better to implement to monitor custom CRD like KSM.

It's OK to close this PR.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[github-actions]

Closed as inactive. Feel free to reopen if this PR is still being worked on.