Posts

Kubespray vs KIND: Which Kubernetes Setup Tool Should You Choose? When it comes to setting up a Kubernetes cluster, two names often come up: Kubespray and KIND (Kubernetes IN Docker). Both are open-source, both simplify Kubernetes cluster provisioning, but they serve different purposes. Let’s explore their differences, use cases, and when to choose one over the other. What is KIND? KIND is a tool for running local Kubernetes clusters using Docker container “nodes”. It’s primarily aimed at testing Kubernetes itself, CI workflows, and local development. ...

Common kube-apiserver Errors and How to Fix Them If you’re working with Kubernetes long enough, you’ll eventually run into strange behavior — and often the root cause is hidden inside the kube-apiserver. This component is the front door to your cluster, handling all requests and coordinating most actions. When it goes wrong, it can affect everything. Let’s look at common issues with the kube-apiserver and what to do about them. ...

What is APM? APM stands for Application Performance Monitoring or Application Performance Management. It’s a set of tools and practices that help you track, monitor, and optimize the performance of your applications. In simple terms, APM helps answer: Why is my app slow? What happens when users interact with the app? Where exactly is the performance bottleneck? Why Use APM? Imagine a user clicks a button on your website and it takes forever to respond. With APM, you can: ...

CoreDNS is one of those quiet heroes in your Kubernetes cluster. It doesn’t get much attention—until DNS stops working, and suddenly everything breaks. Let’s understand how it works — simply. What Is CoreDNS? CoreDNS is the default DNS server in Kubernetes. It’s what helps your pods resolve names like my-service.default.svc.cluster.local to an actual IP address. It’s not just a DNS server. It’s modular, pluggable, and built for cloud-native environments. Why Is DNS Needed in Kubernetes? In Kubernetes, everything is dynamic: ...

Why Add a Custom DNS Zone? Adding a custom DNS zone in CoreDNS can be useful for: Internal testing (e.g., *.local or *.internal) Service discovery for non-Kubernetes services Custom mappings and overrides Step-by-Step Guide 1. Edit the CoreDNS ConfigMap kubectl -n kube-system edit configmap coredns Add a new zone block like this: apiVersion: v1 kind: ConfigMap metadata: name: coredns namespace: kube-system data: Corefile: | .:53 { errors health kubernetes cluster.local in-addr.arpa ip6.arpa { pods insecure fallthrough in-addr.arpa ip6.arpa } forward . /etc/resolv.conf cache 30 loop reload loadbalance } internal.test:53 { hosts { 10.10.10.10 service1.internal.test 10.10.10.11 service2.internal.test fallthrough } } 2. Restart CoreDNS kubectl -n kube-system rollout restart deployment coredns 3. Test the Zone From any pod: ...