monitoring

Preparation 1. Deploy metrics server First, we need to deploy metrics server before deploying kubernetes dashboard 1 kubectl apply -f https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml if you have a problem that metrics-server’s pod not running, probably because tls issue, so add --kubelet-insecure-tls on args section of deployment, then rollout restart it. Kubernetes dashboard 2. Deploy kubernetes dashboard 1 kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml 3. Make user credential Service account 1 2 3 4 5 6 7 kubectl apply -f - << EOF apiVersion: v1 kind: ServiceAccount metadata: name: admin-user namespace: kubernetes-dashboard EOF Cluster Role Binding 1 2 3 4 5 6 7 8 9 10 11 12 13 14 kubectl apply -f - << EOF apiVersion: rbac....

A simple way to keep an eye on your VMs is by using Node Exporter, and Prometheus. These tools are free and open-source. Node Exporter as an agent works inside your VM, collecting data like CPU usage, memory, disk, and network then sending those metrics to Prometheus. Prometheus as datasource, collecting every metrics from every agent store and keep them within range of time that has been set. 1. Setup node exporter Make user for node exporter systemd service...