kubernetes

Kubernetes controllers use informers to connect to APIServers, it has a famous LIST-WATCH mechanism in it. The problem with this is, when an APIServer crashes / restarts, all controllers connected to the APIServer will be forced to reconnect, and send the LIST request again to APIServer. LIST requests are very expensive, while WATCH requests are quite cheap. All controllers sending LIST requests to an APIServer in a short time window will make sure that APIServer is overwhelmed again, and never succeed in starting up....

We sometimes need to do large-scale Kubernetes ops. Shell script is a great way to automate this. I think the combination of kubectl + shell / nodejs is hugely underrated. I decided to write a blog to share my best practices. (to be continued)

At work, we manage hundreds of Kubernetes clusters. Some (in production network) requiring proxy, while others (in dev network) doesn’t. How can seamlessly access all of them from my terminal? I built a tool utilizing bash function to solve this elegantly. (to be continued)