You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`-` The Kubernetes cluster has features the client-go library can't use (additional API objects, etc).
56
+
57
+
#### Container Image
29
58
30
59
The latest container image can be found at:
31
60
*`quay.io/coreos/kube-state-metrics:v1.0.1`
@@ -35,7 +64,7 @@ The latest container image can be found at:
35
64
The recommended docker registry for kube-state-metrics is `quay.io`. kube-state-metrics on
36
65
`gcr.io` is only maintained on best effort as it requires external help from Google employees.
37
66
38
-
## Metrics Documentation
67
+
###Metrics Documentation
39
68
40
69
There are many more metrics we could report, but this first pass is focused on
41
70
those that could be used for actionable alerts. Please contribute PR's for
@@ -53,7 +82,7 @@ additional metrics!
53
82
54
83
See the [`Documentation`](Documentation) directory for documentation of the exposed metrics.
55
84
56
-
## Resource recommendation
85
+
###Resource recommendation
57
86
58
87
Resource usage changes with the size of the cluster. As a general rule, you should allocate
59
88
@@ -67,7 +96,7 @@ For clusters of more than 100 nodes, allocate at least
67
96
68
97
These numbers are based on [scalability tests](https://github.com/kubernetes/kube-state-metrics/issues/124#issuecomment-318394185) at 30 pods per node.
69
98
70
-
## kube-state-metrics vs. Heapster
99
+
###kube-state-metrics vs. Heapster
71
100
72
101
[Heapster](https://github.com/kubernetes/heapster) is a project which fetches
73
102
metrics (such as CPU and memory utilization) from the Kubernetes API server and
@@ -96,36 +125,36 @@ for metric collection at all and instead implement their own, but
96
125
Having kube-state-metrics as a separate project enables access to these metrics
97
126
from those monitoring systems.
98
127
99
-
# Setup
128
+
###Setup
100
129
101
130
Install this project to your `$GOPATH` using `go get`:
102
131
103
132
```
104
133
go get k8s.io/kube-state-metrics
105
134
```
106
135
107
-
## Building the Docker container
136
+
####Building the Docker container
108
137
109
138
Simple run the following command in this root folder, which will create a
110
139
self-contained, statically-linked binary and build a Docker image:
111
140
```
112
141
make container
113
142
```
114
143
115
-
# Usage
144
+
###Usage
116
145
117
146
Simply build and run kube-state-metrics inside a Kubernetes pod which has a
118
147
service account token that has read-only access to the Kubernetes cluster.
119
148
120
-
## Kubernetes Deployment
149
+
####Kubernetes Deployment
121
150
122
151
To deploy this project, you can simply run `kubectl apply -f kubernetes` and a
123
152
Kubernetes service and deployment will be created. The service already has a
124
153
`prometheus.io/scrape: 'true'` annotation and if you added the recommended
125
154
Prometheus service-endpoint scraping [configuration](https://raw.githubusercontent.com/prometheus/prometheus/master/documentation/examples/prometheus-kubernetes.yml), Prometheus will pick it up automatically and you can start using the generated
126
155
metrics right away.
127
156
128
-
# Development
157
+
####Development
129
158
130
159
When developing, test a metric dump against your local Kubernetes cluster by
0 commit comments