I documented my journey configuring a Kubernetes Cluster on a Raspberry Pi using Ansible, totaling 50 minutes. I deployed three Raspberry Pi 4 Model B 8GB as master nodes and one Raspberry Pi 3 Model B as a worker. After installing Ansible, Flash, and kubectl, I prepared the SD cards with customized cloud-config.yml files. Ansible inventory was configured accordingly. Additional SSH and system adjustments were made on each node. Customizations were applied, and the Kubernetes cluster setup was initiated using the Ansible playbook. Troubleshooting tips were provided for potential issues. Finally, the Kubernetes Pi Cluster with Ansible was ready for use.

I've successfully set up my Private Registry for the Kubernetes Cluster on Raspberry Pi. With this, I have full control over the Docker registry, enhancing overall performance. The process involves creating a self-signed certificate, installing it on master and leaf nodes, and deploying the registry. Utilizing the private registry with Jenkins is seamless: tagging, pushing, and pulling images. Troubleshooting tips include updating the hosts file and trusting the certificate at the OS level. Now, my Kubernetes Cluster benefits from a personalized, efficient private registry.

I've successfully set up Jenkins Agents for my Kubernetes Cluster, enhancing its capabilities for automated build, test, and scalable deployment pipelines. Following Docker image creation for the Jenkins agent on the Raspberry Pi, I configured Jenkins for scalability. Adjustments included setting the inbound agent protocol and configuring Kubernetes cloud settings. Creating Jenkins jobs and scheduling builds demonstrated the functionality, with agents initially suspended and later executing jobs successfully. The troubleshooting tip highlighted the importance of naming the container as jnlp. My Jenkins on Kubernetes Cluster is now fully operational, ready for future pipeline configurations.

I've successfully set up Jenkins on my Kubernetes Cluster, streamlining build, test, and deployment pipelines. Following a Docker image creation for Jenkins on the Raspberry Pi, I deployed it to the Kubernetes Cluster. Troubleshooting involved building a custom Docker image due to ARM architecture limitations. Additionally, I addressed a service account error by creating the necessary role and role binding. Now, I can access Jenkins and proceed to configure Jenkins Agents for Kubernetes in the next post, enhancing automation within my cluster.