Today, I’ll explain how to setup GlusterFS volume storage on ubuntu server. Currently, I’m ready to re-build k8s cluster on the volume storage service like Ceph or GlusterFS. However, Raspberry Pi is little bit sufficient to run the Ceph and K8s clusters on the same board. So, I’ll use the GlusterFS as a backend volume service of my K8s cluster on 4 Raspi servers.

I’m sorry, these contents are Korean only!!

In this post, I’ll explain how to build a container using buildah and upload that into the private registry. We can set the default registry in the crio’s config file, but this method is not good because some images doesn’t matched for the arm64 environment system even if that had been provided from quay or docker.io. So that reason, we keep the blank default registry settings.

Now we build the private registry. The private registry is very helpful, if you run the kubernetes cluster in the dedicated network or test your built micro-service before publishing. But, the default deploy config of the docker-registry uses emptyDir and it cannot keep the registry volumes. To keep the uploaded images permanently, the image data should be stored on the persistent volumes like Ceph, NFS, iSCSI, and etc…

To run your services and pods, you need to build and upload the container images on the registry service. However, many public registry services charge fees for use, so that we need to build the private registry service for a personal and temporary uses.