Networking

Kubernetes Konnectivity xfr-channel-size Configuration I have often encountered situations where network connectivity between the API server and cluster nodes becomes complicated. Firewalls, network policies, and VPC configurations can block direct communication. This is where Konnectivity comes in. It provides a network proxy system that tunnels traffic through these barriers. During my work with Konnectivity, I encountered the warning message Receive channel from agent is full in my cluster logs. I asked the Kubernetes community for help but didn’t receive a response. I also couldn’t find any documentation explaining what this warning meant or how to fix it, or even any documentation about this component :(. So, this led me to reading the source code to understand what xfr-channel-size actually does, which controls data buffering, and getting it right can make a difference in how your cluster performs under load. ...

This blog post is a collection of my personal notes on networking. For a long time, I had to jump between different notebooks to connect concepts; from core networking theory, to Linux internals, all the way up to Kubernetes and CNI. This post is my attempt to combine all those notes into a single, logical document. We’ll follow a step-by-step path. We’ll start with fundamental network concepts, then see how those are implemented in Linux, which is the foundation for most modern virtual networking. Finally, we’ll see how Kubernetes builds on top of it all. ...

I’ve always found the best way to learn something is to try and write it down. This post is the result of that process, a collection of my personal notes (zettelkasten) aimed at connecting the dots between three fundamental concepts in Linux: inodes, file descriptors, and sockets. So, this post is just a cleaned-up version of my personal notes, explaining how inodes (representing files on disk), file descriptors (used by programs), and sockets (for network communication) all fit together. ...