When I started to dig deeper into my previous master-slave Jenkins setup, I realized that my configuration needs more customizations. In the real-world scenario, we want to use our Jenkins to build or proceed with given tasks using special utilities. For example, we want to run the Ansible playbook as a scheduled Jenkins job. Unfortunately, it won’t work with the default slave image because the Ansible binaries are missing. Today, I want to show you how to fix it, and add more utilities to our Docker Jenkins-Slave image.
As I promised in the last post, I’ll show you how to set up our first Kubernetes application deployment. For the purpose of this demo, I have selected the Jenkins. I hope this tool is well known by all of you interested in modern DevOps CI/CD approach. Building the Jenkins on the top of Kubernetes is not only very easy, but also extremely powerful because it gives us the possibility to autoscale our build environment by automatically spin up new docker instances for the requested jobs.
Kubernetes dashboard is one of the key components of each cluster deployment. As stated on official GitHub repository of this project, Kubernetes Dashboard is a general purpose, web-based UI for Kubernetes clusters. Although rancher dashboard provides much information about our cluster configuration, its poor in terms of low-level in information about our application deployment, pod status and many other details about our cluster. In this post, I’m going to show you how to configure and access this Web UI.
Welcome to the part two of my Kubernetes practical tutorial. It’s time to say a bit more about the Rancher. If you followed my previous installation guide, your new instance should consist of two EC2 t3.medium instances. One is the Rancher management host, the second one is the worker (first k8s cluster node). Let’s go for a quick walk through the Rancher GUI.
Recently, I started to learn and discover deeper the world of containers. When it comes to containers, one of the most important tools in today’s days is the Kubernetes. Unfortunately, it’s not easy to find a good solution for k8s. It comes in various products, mainly tailored to the given infrastructure. As a result, we have products like AWS EKS (Amazon Elastic Container Service for Kubernetes), GKE (Google Kubernetes Engine) or AKS (Azure Kubernetes Service) – managed by main cloud providers. Kubernetes comes also in form of on-premises solutions, here we have products like Cloudstack, Kubespray or Kubeadm. Everything depends on your needs, current infrastructure and expectations.