Kubernetes 101 – The constructs
In our last post, we got our base lab up and running. In this post, I’d like to walk us through the four main constructs that Kubernetes uses. Kubernetes defines these constructs through configuration files which can be either YAML or JSON. Let’s walk through each construct so we can define it, show possible configurations, and lastly an example of how it works on our lab cluster.
Pods
Pods are the basic deployment unit in Kubernetes. A pod consists of one or more containers. Recall that Kubernetes is a container cluster management solution. It concerns itself with workload placement not individual container placement. Kubernetes defines a pod as a group of ‘closely related containers’. Some people would go as far as saying a pod is a single application. I’m hesitant of that definition since it it seems too broad. I think what it really boils down to is grouping containers together that make sense. From a network point of view, a pod has a single IP address. Multiple containers that run in a pod all share that common network name space. This also means that containers Continue reading