Common Kubernetes troubleshooting tasks

If you are working on?kubernetes ?or heard about that with someone working on kubernetes, says Kubernetes is complex and hard to manage or troubleshoot. Same time you may see in kubernetes cluster either one, goes wrong sometimes.

You may experienced most common issues are container unavailable or pod doesn’t respond. With that any guess how your DevOps/SRE teams figures out the cause of the issue and fix it?

In this section will see what common scenarios your DevOps/SRE teams are may encounter, and how they address them.

1. Node unavailable

One of the key reason Kubernetes known for High Availability, where kubernetes automatically distribute the applications across multiple available nodes hosted on physical datacenter or virtual machines. If there is some availability issue, there is likely an insufficient number of available nodes.

If you see any node related issue, make sure you have enough nodes assigned to cluster. Any High availability cluster should contain minimum two nodes, please note we are speaking about kubernetes master node.

Even with enough nodes, you may find that nodes fail after you’ve set up and joined them to a cluster. One way to address this issue is to enable auto-recovery of any VMs that host nodes. Most cloud providers and on-premises VM platforms offer auto-recovery features that restart a failed machine automatically.

Increasing the number of servers in a cluster may also improve node availability, even if the number of nodes stays the same. When you spread nodes across multiple servers, you limit the harm done to your cluster by a server failure.

Continue Reading on Common Kubernetes troubleshooting tasks - FoxuTech