Day 34 of #40daysofkubernetes challengeIn this blog I will be covering how to upgrade a Kubernetes cluster to a newer version using kubeadm - doing it the safe way, one node at a time, without taking the whole cluster down. The idea A clus6d ago · 4 min readsaranbuilds.hashnode.dev
Day 33 of #40daysofkubernetes challengeThe problem Ingress solves Earlier in the challenge I used NodePort and LoadBalancer to expose a service outside the cluster. They work, but they do not scale well. A NodePort exposes raw node IPs on 6d ago · 4 min readsaranbuilds.hashnode.dev
Day 31 of #40daysofkubernetes challengeIn the previous blog I covered how DNS works in general. In this blog I will be covering CoreDNS - the DNS that runs inside a Kubernetes cluster and lets pods find each other by name instead of by IP.6d ago · 4 min readsaranbuilds.hashnode.dev
Day 30 of #40daysofkubernetes challengeThis day was a concepts one - understanding DNS. Not the Kubernetes-specific DNS, just DNS itself, because so much of what I had been debugging in the cluster came down to name resolution, and it help6d ago · 3 min readsaranbuilds.hashnode.dev
Day 29 of #40daysofkubernetes challengeA few days ago I looked at Docker volumes - how a container keeps data outside itself so it survives a restart. In this blog I will be covering the Kubernetes version of that idea: PersistentVolumes a6d ago · 4 min readsaranbuilds.hashnode.dev
