You’ve immersed yourself in the containerization world for a while. Kubernetes
is the next frontier, but the concept of a pod is a little foreign. When you
first learn about pods it’s hard to think of a use case where a pod is a more
natural fit than a container. Plus, the tutorials and documentation cover what
a pod is rather than why you should use one. It’s easy to think up “trivial”
use cases, but how are people actually using pods in the real world?
Well, wonder no longer. We’re cover five real world use cases for pods. These
should provide some insight into when and why we should use pods.
You’ve started your Kubernetes cluster, and you’re all ready to move apps
inside. Only one question remains: what happens when services are not hosted in
Kubernetes? How can you reference these services?
Backend and frontend services should interoperate easily. To do that, Kubernetes
has three
service types:
ClusterIP, NodePort, and LoadBalancer. But which should you use?
ClusterIP and LoadBalancer seem self-explanatory, but what would you use
NodePort for? Even though there are only three options, it can get a little
confusing!