Cluster Troubleshooting

Objective

This guide explains how to use Cluster Troubleshooting on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.

Before you begin

• Sign in with an account permitted to manage the relevant environment.
• Confirm the target environment, region and resources before saving changes.
• Create a backup or rollback plan before changing a production system.

PackageKubernetes Clusterby Ruk-Com is a very complex product with many steps required to set up the solution. Because of this, individual actions can fail for various reasons, which should be analyzed to prevent problems in the future. Below we outline the main troubleshooting steps between steps and for multiple Log files:

• K8s Installation
• Events Tracking
• Pod Logs

Installing K8s

Installing a Kubernetes cluster is a complex process. Instead, it is fully automated with built-in error handling mechanisms. The platform automatically processes common issues and shows the root cause directly in the dashboard. In this case, for more complicated problems, you can press the buttonSend Reportto the support team via the appropriate widget

The report contains the installation log, error messages, and all other required debugging information.

Additionally, the package automatically checks all cluster components after installation. Relevant details can be found in the file. /var/log/k8s-health-check.log On the master node, a dedicated utility script checks the health of the following components: Weave CNI Plugin, Ingres Controller, Metrics Server, Kubernetes Dashboard, Node Problem Detector, Monitoring Tools, Remote API, NFS Storage, Sample App.

If the Performance Monitor is unable to check the Running status of a component An appropriate notification is displayed in the success box. Here, such warnings are not always due to a cluster malfunction (for example, a deployment might be in progress). You can run the kubectl get pods –all-namespaces command. To check the status of your pods, if they are all running, your cluster is working fine. Otherwise, contact platform support and attach the K8-related log from the /var/log directory.

Events Tracking

You can use kubectl or Kubernetes Dashboard to track and analyze events for a specific or all namespaces in one place. (requires sufficient permissions):

• EventsIn the Kubernetes Dashboard
• Example output from the command kubectl get events -n $namespace

Pod Logs

After scheduling the pod to run on a free node, you can follow the appropriate log via:

• Kubernetes Dashboard- Click on the pod page and click the Logs button in the top right corner.
• kubectl- Use commands forpods management

For example, these logs can help find the root cause of the “Back-off restart failed container” event for your pod.