Monitoring Rancher Master

As mentioned earlier, eG Enterprise provides a specialized model for monitoring Rancher Master (see Figure 1).

Figure 1 : Layer model of Rancher Master

Using the metrics reported, administrators can quickly find accurate answers for the following performance questions:

  • Is the current utilization of CPU, memory, and disk optimal on each node?

  • Is the memory utilization on the node optimal?

  • Are there any performance bottlenecks in CPU or memory resources?

  • Is the disk usage on the master node nearing capacity?

  • Are there any disk I/O errors or performance issues on the master node?

  • Is the Kubernetes API Server operating optimally on the master node?

  • Is the Kubernetes API Server responding with low latency or encountering timeouts?

  • Is the health of the etcd server on the master node normal? Are there any causes for concern?

  • Are there any issues with etcd leader election or unavailability?

  • Are the kube-scheduler and kube controller manager running without issues?

  • Are there any failed or stuck pods in the system, including critical control plane components?

  • Are the Kubernetes audit logs showing relevant information for system events or errors?

  • Are there any certificate expiry warnings for Kubernetes components?

  • Are the network connections between the master node and worker nodes stable?

  • Are network policies correctly applied, and is there no connectivity issue between nodes?

  • Is there any abnormal network latency between the master node and components like etcd or the API Server?

  • Are the Kubernetes control plane components auto-scaling based on resource demand?

  • Are there any frequent pod crashes or restarts related to Kubernetes components on the master node?

  • Are there any known security vulnerabilities or misconfigurations in the master node setup?

By effectively monitoring Rancher Master nodes, organizations can enhance performance, security, and overall reliability of their applications.

These layers are similar to the Kubernetes Master monitoring model; hence, refer the Monitoring Kubernetes Master node for a detailed discussion on each of the layers of Figure 1.