IntégrationsVirtualisation et conteneurs
Surveiller Kubernetes / k3s avec DumbMonit
A cluster through its API: nodes not ready or under pressure, pods crash looping or stuck pending, workloads missing replicas, volume claims never bound.
DocumentationSite officiel : Kubernetes
Les descriptions des produits sont en anglais, comme dans le produit. Les libellés de la page suivent votre langue.
Ce que DumbMonit surveille
A cluster through its API server: nodes that are not Ready or under pressure, pods crash looping or stuck Pending, Deployments, StatefulSets and DaemonSets missing replicas, volume claims that never get bound, and the warning events of the last hour.
Usage typique. Cluster: nodes not ready, pods crash looping or pending, workloads missing replicas, stuck volume claims
Exemples
- k3s
- kubeadm cluster
- k0s
- MicroK8s
- Talos
Comment il se connecte
Ce qu'il faut
- Service account tokenThe token of the dumbmonit service account, read from its dumbmonit-token Secret.
Ports réseau à ouvrir
6443/TCPAPI server (HTTPS, default)
Étapes de mise en place: Create a read-only service account for DumbMonit
Create the service account.
kubectl create serviceaccount dumbmonit -n kube-systemCreate a ClusterRole that can only get and list what DumbMonit reads.
kubectl create clusterrole dumbmonit-read --verb=get,list --resource=nodes,pods,persistentvolumeclaims,events,deployments.apps,statefulsets.apps,daemonsets.appsBind the role to the service account.
kubectl create clusterrolebinding dumbmonit-read --clusterrole=dumbmonit-read --serviceaccount=kube-system:dumbmonitCreate a token that does not expire, then print the token and the cluster CA in base64.
echo '{"apiVersion":"v1","kind":"Secret","metadata":{"name":"dumbmonit-token","namespace":"kube-system","annotations":{"kubernetes.io/service-account.name":"dumbmonit"}},"type":"kubernetes.io/service-account-token"}' | kubectl apply -f - kubectl -n kube-system get secret dumbmonit-token -o jsonpath='{.data.token}' | base64 -d kubectl -n kube-system get secret dumbmonit-token -o jsonpath='{.data.ca\.crt}'In DumbMonit, enter the API server address (for example https://k3s.lan:6443), paste the token as Service account token and the CA as Cluster CA certificate.
À savoir. On k3s, run each command as sudo k3s kubectl. The API server certificate only lists its own names and addresses: use one it lists, or tick Accept an unverifiable certificate.