In my recent endeavor, I spent 40 minutes setting up Gitea on my Kubernetes Pi cluster, granting me absolute control over personal Git repositories. I seamlessly integrated MySQL, using Docker images and Kubernetes configurations. The meticulous setup involved creating necessary paths on an external HDD, configuring persistent volumes, and ensuring a smooth deployment. I prepared MySQL for Gitea, creating a user, database, and granting privileges. Gitea installation via Docker and subsequent exposure to external access using NodePort were executed flawlessly. A troubleshooting tip addressed a MySQL access issue. Now, my Gitea on Kubernetes Pi Cluster is fully operational for efficient repository management.

I dedicated 45 minutes to set up Gitea on my Raspberry Pi cluster using MicroK8s. Gitea, a self-hosted Git service, grants my team cost savings and enhanced server control. I ensured a smooth installation by preparing MySQL, creating required paths on an external HDD, and configuring persistent volumes. Following MySQL setup, I seamlessly prepared the database and moved on to setting up Gitea with Docker, utilizing a docker-compose.yml file. After injecting images into MicroK8s cache, I exposed Gitea externally using NodePort. Troubleshooting tips were handy, addressing MySQL connection issues. My self-hosted Git service is now ready for efficient collaboration.

Expanding my Raspberry Pi Cluster's storage with an external 640GB USB hard disk took 35 minutes. After mounting the external storage and addressing troubleshooting issues, I configured MicroK8s default storage to utilize the added space. Despite encountering errors, a reset and careful configuration solved the problem. Adding leaf nodes for MicroK8s and troubleshooting service unavailability for the dashboard completed the setup. I also disabled and re-enabled addons, ensuring a smooth integration of external storage with my MicroK8s cluster. Accessing the Kubernetes dashboard and checking nodes confirmed a successful expansion.

In the second part of my MicroK8s adventure on Raspberry Pi 4 Model B 8GB, I spent 45 minutes adding low-cost Raspberry Pi nodes to enhance cluster performance. Utilizing two older Pi 3B devices with Ubuntu Server (64-bit), I updated the OS, installed MicroK8s, and adjusted configurations. The master node initiated new node creation with "sudo microk8s add-node," copying the output to each node. Successful integration was confirmed with "microk8s kubectl get node." Excited to explore Kubernetes possibilities and gradually shift CI/CD pipelines to this lightweight cluster. Stay tuned for more on its diverse use cases!

I recently spent 40 minutes setting up MicroK8s on my new Raspberry Pi 4 Model B 8GB. Opting for a headless install due to a lack of a microHDMI cable, I used Ubuntu Server (64-bit) for the 64-bit requirements of MicroK8s. After initial setup, including changing the hostname and enabling memory cgroup, I installed MicroK8s, ensuring compatibility by adding my user to the MicroK8s group. Verification and usage of MicroK8s followed, with additional steps for enabling services like the dashboard. Troubleshooting involved switching to a 64-bit OS and finding the Pi's IP using nmap. Excited to explore MicroK8s on my Raspberry Pi!