In my previous article, I configured the Kubernetes cluster with a private Docker registry. In this one, I aim to convert this site to a Docker container and deploy it to the cluster. This time there isn’t a nice DigitalOcean tutorial, but Docker is already nice to work in. Setting up Docker This site generates using Hugo. Building it is as simple as running the Hugo command. hugo To build the image, it’s important to know how the site’s built.

In my previous article, I set up a Kubernetes cluster with hosting, ingress, and TLS. This time my goal was to deploy a private Docker registry on the cluster. Then upload an image to the registry and deploy it on the cluster. Again, there’s documentation on how to do that via DigitalOcean. This was my starting point, and I made a few adjustments along the way. DNS My first task was setting up another A record to point to the cluster.

This article describes my experience re-hosting this site on DigitalOcean with Kubernetes. If you’ve read my previous posts, you know this site is staticly generated with Hugo. I deploy using Git on Azure App Services. As I move deeper into total containerization, I’ve started looking for a host that’s more tailored for many small containers. Although I enjoy App Services for their simplicity, I’ve run into publishing issues when using Docker.