Explained: CoreDNS

You deploy a new service to your Kubernetes cluster. The pods come up healthy. You open a shell inside one of them and try to reach another service by name — http://payments-service — and nothing happens. Timeout. You try the full name: http://payments-service.billing.svc.cluster.local . Still nothing. You try the service's ClusterIP directly, and it works fine. Something in the cluster is resolving names, but it's not resolving yours. If … Read More

Architecture: How Kubernetes Works

You have a fleet of containers. They need to run reliably, scale under load, recover from failures, and communicate with each other — all without you manually SSHing into servers at 2am. That's the problem Kubernetes was built to solve. This post walks through how Kubernetes is actually architected: what the pieces are, how they talk to each other, and why they were designed that way. No prior Kubernetes experience needed — just a general com… Read More

Explained: Node Affinity in Kubernetes

When you deploy a workload to a Kubernetes cluster, the scheduler makes a decision: which node should run this pod? By default it balances across available nodes, picking whichever has the capacity. Most of the time that's fine. But in the real world, infrastructure is rarely uniform. You've got GPU nodes for ML workloads, high-memory nodes for caching tiers, nodes in specific availability zones for compliance, and bare-metal nodes for … Read More