Enabling kube-state-metric custom resource config to monitor HCP API

[venkateshsredhat]

Enabling kube-state-metric custom resource config to monitor HCP API .
Why ?
We eventually want to get rid of the RMO completely .

Exposed metric for KubeAPI server availability :

hostedClusterAPI_kubeapiserver_available{_id="48522a00-b130-4677-b101-d67398f934ca", api_url="api-int.ves.3gh6.usw3ves.hcp.osadev.cloud", container="kube-state-metrics", customresource_group="hypershift.openshift.io", customresource_kind="HostedCluster", customresource_version="v1beta1", endpoint="http", instance="10.128.64.255:8080", job="kube-state-metrics", name="ves", namespace="ocm-arohcpdev-2ohhvbnl0heak5clamitmqi5kmvvdefg", pod="arohcp-monitor-kube-state-metrics-556788dd88-8cdrm", service="arohcp-monitor-kube-state-metrics", status="True"}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: venkateshsredhat
Once this PR has been reviewed and has the lgtm label, please assign janboll for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• dev-infrastructure/OWNERS
• observability/OWNERS

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

[venkateshsredhat]

/test e2e-parallel

[openshift-ci]

@venkateshsredhat: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/mega-linter	e247c0c	link	true	/test mega-linter
ci/prow/verify	e247c0c	link	true	/test verify
ci/prow/test-unit	e247c0c	link	true	/test test-unit
ci/prow/e2e-parallel	e247c0c	link	true	/test e2e-parallel

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.