You got your Docker image ready. Now how do you run it? Pods? ReplicaSets? Services? Fear no more, here comes the cavalry.
This is a series of 5 articles. If you want to check Part I, follow the following link:
I’ll try to make this as clear as possible because there are a few steps to follow that might seem a lot the first time. There are three big steps as listed below:
So you managed to push your Docker images to the Container Registry, but you’re getting a dreaded
ImagePullBackoff error when your Pods are trying to start. Even though there are several reasons that could make this happen (i.e.: a typo in your YAML files), it could simply be that your cluster is lacking the permissions to fetch them. On GCP, by default, clusters have access to the Container Registry automatically if both are in the same GCP project. But if you have to access images from other projects or you chose another provider, that’s another story. Enter
So you’ve heard about Kubernetes, you know it’s something about clusters, high availability and…deployments?. But every time you hear about a new technology you say to yourself “Oh, here we go again. Another whole pack of documentation pages that will take me ages to read until I can have something working and I don’t even know if it’s worth the effort”. I said that. A million times. And I’ll surely keep doing it. So this should be a super-packed doc that will give you a slightly more than basic understanding of the platform, and hopefully give you an idea if…
Around three years ago while I was working at Debut, we started using Kubernetes. We made the decision after realising we needed a flexible space to deploy services that were critical for the platform to grow. It was a whole new world of containerisation on top of the already widely famous Docker. From the very beginning I’ve been learning how to tackle many aspects of running a production-ready cluster — this is a little bit of my experience so far that I wanted to share.
Besides any specific technology, the main points that you can draw out of this series…
Technology enthusiast. Less is more.