You are looking at the documentation of a prior release. To read the documentation of the latest release, please
visit here.
New to Kubed? Please start here.
Monitoring Kubed
Kubed has native support for monitoring via Prometheus. Kubed operator exposes Prometheus native monitoring data via /metrics endpoint on :56790 port. You can setup a CoreOS Prometheus ServiceMonitor using kubed-operator service. To change the port, use --web.address flag on Kubed operator.
$ kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
kube-addon-manager-minikube 1/1 Running 0 33m
kube-dns-1301475494-hglm0 3/3 Running 0 33m
kubed-operator-3234987584-sbgrf 1/1 Running 0 19s
kubernetes-dashboard-l8vlj 1/1 Running 0 33m
$ kubectl port-forward $(kubectl get pods --all-namespaces -l app=kubed -o jsonpath={.items[0].metadata.name}) -n kube-system 56790
Forwarding from 127.0.0.1:56790 -> 56790
E0727 03:50:34.668103 22871 portforward.go:212] Unable to create listener: Error listen tcp6 [::1]:56790: bind: cannot assign requested address
Handling connection for 56790
Now, open the URL http://127.0.0.1:56790/metrics in your browser.
Next Steps
- Learn how to use Kubed to protect your Kubernetes cluster from disasters here.
- Need to keep configmaps/secrets synchronized across namespaces or clusters? Try Kubed config syncer.
- Want to keep an eye on your cluster with automated notifications? Setup Kubed event forwarder.
- Out of disk space because of too much logs in Elasticsearch or metrics in InfluxDB? Configure janitors to delete old data.
- Wondering what features are coming next? Please visit here.
- Want to hack on Kubed? Check our contribution guidelines.