Posts
Kubernetes Application Troubleshooting
· β˜• 4 min read
Setting Reasonable Req and Limit Without Req and Limit set, when an application’s CPU or MEM spikes, it harms other Pods on the same node, and can even cause cluster nodes to be crushed one after another. Req and Limit have four values in total. If only some of them are set, then when node resource usage reaches the threshold preset by Kubelet, Kubelet evicts Pods in the order Guaranteed > Burstable > Best-Effort

Kubernetes Cluster Troubleshooting
· β˜• 6 min read
FailedCreatePodSandBox Error Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:402: getting the final child's pid from pipe caused: EOF: unknown Resolution Clear the cache 1 echo 3 > /proc/sys/vm/drop_caches Cause Too much memory fragmentation calico-node Keeps Restarting increase max user Error runtime: failed to

How to Repair a Kubernetes Cluster After Changing IPs
· β˜• 3 min read
A record of repairing a cluster failure caused by an IP change. There are two clusters: one single-node (allinone) cluster, and one four-node cluster (3 masters, 1 node). 1. Update the Etcd Certificates [On every Etcd node] Back up the Etcd certificates 1 cp -R /etc/ssl/etcd/ssl /etc/ssl/etcd/ssl-bak View the domains

A Deep Dive into Kubernetes Network Packet Forwarding
· β˜• 22 min read
This article is translated from https://learnk8s.io/kubernetes-network-packets, not word for word, with some of my own understanding worked in. By reading this article, you can learn how packets are forwarded inside and outside Kubernetes, starting from the original web request all the way to the container hosting the application. Kubernetes Network Requirements Before diving into the details of how packets flow through a Kubernetes cluster, let’s first clarify Kubernetes’ requirements for networking.

SRE Goes Left, DevOps Goes Right
· β˜• 4 min read
1. A Process Divorced from Responsibility Is Meaningless Software architecture matches organizational architecture, and this shows up not only in functional boundaries but even more in the division of responsibilities. Only clear responsibility boundaries can build good team collaboration and growth. Every team and every person should understand their own goals β€” what they should take on and what they should stay out of β€” and invest their time and energy in things that benefit the primary goal, rather than sinking into trivia.