GuRuTuX

A Service has an IP address that no machine owns and no process listens on, yet traffic sent to it arrives at a healthy Pod. This post follows that traffic step by step, from the control plane to the Linux kernel.

I started learning Kubernetes tonight. I did not begin with the YAML. I went straight to the architecture, because I wanted to understand what the pieces are and how they talk to each other before writing a single manifest. This post is a full explanation of the architecture in the diagram below, one component at a time, in plain language.

The persistence of manually drawn diagrams in technical documentation is an inefficiency bordering on the absurd. We operate in environments demanding precision, version control, and collaboration, yet many still resort to clicking, dragging, and aligning shapes in graphical editors like digital finger-painters. The resulting artifacts – often opaque binary files – clutter repositories, resist meaningful diffing, and become instantly outdated. This is not a complex problem. It has a straightforward, logical solution.

MySQL binary Log replication is one the most used feature in MySQL flavoured Databases as it is the most simple way to replicate data changes across several MySQL nodes. And because it is an Asynchronous replication it has low to no impact on the Master node(s).

A file is a collection of data blocks and has an inode number which holds metadata about this file.