undefined | Better HN

0 pointsregnerba7y ago0 comments

We don't have 100, but definitely more than 20. A quick look at a random node from our cluster:

- 3x ingress pods (1 for an internal load balancer, 2 for an external load balancer)

- 1x cert-manager

- 2x production version of internal app01

- 2x staging version of internal app02

- 1x fluentd

- 1x elastalert

- 1x kubewatch

- 1x prometheus node exporter

- 1x redis for sentry

- 1x sentry web

- 2x sentry worker

- 4x sourcegraph language servers (there are 9 language servers running across the 4 nodes, this node seems to especially like them)

- 1x thelounge

- 1x staging version of app02

- 2x production version of app02

- 1x kube proxy

- 1x kubedns

- 1x couchdb (small footprint just for testing some things)

the node is just over half provisioned and we are due to add another node to the cluster soon.

0 comments

3 comments · 1 top-level

deepsun7y ago· 2 in thread

What does prometheus node exporter collects from within a pod? I was under impression that to collect node stats you absolutely need to be "outside" any container, i.e. using prometheus-k8s integration so that it pulls nodes stats from k8s api, not nodes themselves).

halbritt7y ago

The kube-state-metrics service runs as part of the kubernetes API and provides container metrics. It replaces heapster.

The node exporter runs as a daemonset on each node and provides node specific metrics like CPU, memory, disk IO, network IO, etc.

The node metrics comes from the node itself.

regnerbaOP7y ago

Not an expert, and this may have changed since I deployed this, but I based most of our deployment on the Prometheus helm chart.

The helm charts include this: https://github.com/helm/charts/tree/master/stable/prometheus...

j / k navigate · click thread line to collapse