This is the fifth in a series of blog posts that will explain the different components of Kubernetes. Primarily because if I can explain it here, I’ll have learned it quite well myself. The first part is about Pods and can be found here. The second part is about Controllers and can be found here. The third part is about Services and can be found here. The fourth part is about Volumes and can be found here.
This is the fourth in a series of blog posts that will explain the different components of Kubernetes. Primarily because if I can explain it here, I’ll have learned it quite well myself. The first part is about Pods and can be found here. The second part is about Controllers and can be found here. The third part is about Services and can be found here. Where does the data go?
This is the third in a series of blog posts that will explain the different components of Kubernetes. Primarily because if I can explain it here, I’ll have learned it quite well myself. The first part is about Pods and can be found here. The second part is about Controllers and can be found here. What is a Service? So you’ve deployed a pod, now how do you access it? How do other pods access it?
This is the second in a series of blog posts that will explain the different components of Kubernetes. Primarily because if I can explain it here, I’ll have learned it quite well myself. The first part is about Pods and can be found here. Why Controllers Before we answer the why, we ought to think about what a controller is. The atomic unit in Kubernetes is the pod. You can create and manage them manually.
This is the start of a series of blog posts that will explain the different components of Kubernetes. Primarily because if I can explain it here, I’ll have learned it quite well myself. Primer on Containers I think most people are at least aware of the existence of containers. Fundamentally they’re a construct used to make an application component self contained & portable. It holds all the libraries and binaries required to run the component.