Currently there's no way to monitor if openshift-state-metrics is failing to start a watch on a specific resource type.

We should instrument this and add it as a metric on health metrics endpoints which defaults to port 81

https://github.com/brancz/kube-rbac-proxy

Hi Team, is there any plans for official releases?

Thanks,
Vikram

Currently if I create a route pointing to an SVC, and then delete the backing SVC, there is no change at all in any of the metrics related to the route.

From an alerting perspective, I would like to know if the route is 'healthy'.

ToDo:

• Investigate how this is handled for Ingress in kube-state-metrics
• Implement a status metric for routes

Move code from https://github.com/wanghaoran1988/openshift-state-metrics to this repo https://github.com/openshift/openshift-state-metrics

We probably cannot follow https://help.github.com/en/articles/transferring-a-repository because it states:

The target account must not have a repository with the same name, or a fork in the same network.

Will let @wanghaoran1988 decide :)

Depends on #23

Once we have jsonnet ready, we can send a PR to cluster-monitoring-operator to have our manifests run by default as part of cluster monitoring

https://github.com/openshift/cluster-monitoring-operator/

error: unable to recognize "manifests/openshift-state-metrics-service-monitor.yaml": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"

https://docs.docker.com/develop/develop-images/dockerfile_best-practices/

Use a Template file to bundle up all the manifests required, so that a user with cluster-admin can get started really quickly with an oc create -f bundle.yaml

Hi,
I don't find any info on which is the minimal version of OpenShift required for openshift-state-metrics.
Is it working with OpenShift 3.7?

Thanks

@wanghaoran1988
Is OPenshift State Metrics compatible to below Openshift version

OpenShift Master:
v3.11.715
Kubernetes Master:
v1.11.0+d4cacc0
OpenShift Web Console:
3.11.715-1.ga7c5920-a7c5920

Since you have already mentioned
This is officially supported in openshift 4.2.
Originally posted by @wanghaoran1988 in #42 (comment)

Can you please confirm since there is no information available on the version details in github page

Can we just use /healthz for this?

I would like to know, even if the different versions are indicated in the branches, if openshift-state-metrics is available in versions 3.9 and 3.11.

$SUBJECT

The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

• release-4.17
• release-4.18

For more information, see the branching documentation.

Similar to the openshift_deploymentconfig_labels metrics that exposes the labels for a given deployment config, we would like to expose annotation metrics. We use like to be able to use this to track usage of certain features like prometheus.io/scrape, prometheus.jvm.io/scrape, as well as some custom annotations that we use for Operators added to our environment.