wbsong111
6290322f1b
- VM stack 10 charts: victoria-metrics-cluster/auth, victoria-logs-cluster, victoria-metrics-agent/alert, opentelemetry-collector, kube-state-metrics, prometheus-node-exporter, alertmanager, perses (JWT/OIDC, Infisical-ready) - ArgoCD ApplicationSet (syncWave) + per-chart dip-values overlays - doc/victoria-metrics-architecture.md, define-chart-resources updates - includes pending working-tree changes (mlflow, kubeflow, apisix, CLAUDE.md) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
24 lines
1.1 KiB
Plaintext
24 lines
1.1 KiB
Plaintext
kube-state-metrics is a simple service that listens to the Kubernetes API server and generates metrics about the state of the objects.
|
|
The exposed metrics can be found here:
|
|
https://github.com/kubernetes/kube-state-metrics/blob/master/docs/README.md#exposed-metrics
|
|
|
|
The metrics are exported on the HTTP endpoint /metrics on the listening port.
|
|
In your case, {{ template "kube-state-metrics.fullname" . }}.{{ template "kube-state-metrics.namespace" . }}.svc.cluster.local:{{ .Values.service.port }}/metrics
|
|
|
|
They are served either as plaintext or protobuf depending on the Accept header.
|
|
They are designed to be consumed either by Prometheus itself or by a scraper that is compatible with scraping a Prometheus client endpoint.
|
|
|
|
{{- if .Values.kubeRBACProxy.enabled}}
|
|
|
|
kube-rbac-proxy endpoint protections is enabled:
|
|
- Metrics endpoints are now HTTPS
|
|
- Ensure that the client authenticates the requests (e.g. via service account) with the following role permissions:
|
|
```
|
|
rules:
|
|
- apiGroups: [ "" ]
|
|
resources: ["services/{{ template "kube-state-metrics.fullname" . }}"]
|
|
verbs:
|
|
- get
|
|
```
|
|
{{- end }}
|