1. go.sum Version Mismatch After Upgrading Go Running the command go build reports an error.
Error message:
missing go.sum entry for module providing package golang.org/x/time/rate; to add Solution:
Update go.sum before go build by running the command go mod tidy.
2. TLS Error Running the command go mod download reports an error.
Clusters that run for a long time often face various kinds of resource exhaustion. On top of that, when disk space runs low, Kubelet will proactively clean up images on its own, adding another source of uncertainty. This article provides some command snippets for cleanup work.
1. Cleaning Up Basic Kubernetes Objects Clean up Pods in Evicted state 1 sudo kubectl get pods --all-namespaces -o wide | grep Evicted | awk '{print $1,$2}' | sudo xargs -L1 kubectl delete pod -n Clean up Pods in Error state 1 sudo kubectl get pods --all-namespaces -o wide | grep Error | awk '{print $1,$2}' | sudo xargs -L1 kubectl delete pod -n Clean up Pods in Completed state 1 sudo kubectl get pods --all-namespaces -o wide | grep Completed | awk '{print $1,$2}' | sudo xargs -L1 kubectl delete pod -n Clean up unused PVs 1 sudo kubectl describe -A pvc | grep -E "^Name:.
1. Calico 1.1 BIRD is not ready 1 kubectl -n kube-system get pod calico-node-xxx stays at 0/1 and never comes up, reporting calico/node is not ready: BIRD is not ready: BGP not established with
Solution:
Calico uses first-found by default, meaning it takes the NodeIP from the first NIC it finds.
1. Background Many build nodes were added to Jenkins using the same Label for pipelines to use, but Jenkins tends to run builds on the same node every time.
This leads to concurrency problems: a single node is overloaded while other nodes sit idle, so the load is extremely unbalanced.