Setting Up a Test/Learning Kubernetes Cluster. Module 1. Lesson 1.5 of the CKA certification.

Introduction:

Containers have revolutionized software development. Unlike traditional virtual machines, such as VMware or VirtualBox, containers allow for more efficient packaging of applications, ensuring their portability and reliability across different environments.

Why is it important to have a local cluster?

If your goal is to get certified in Kubernetes or deploy a cluster in your company, practice is essential. One of the best ways to do this is by setting up your own testing environment.

Initial considerations and prerequisites:

In this tutorial, I’ll show you how to configure a Kubernetes cluster with a Master node and two Worker nodes in a virtual machine using VirtualBox. Since Kubernetes is designed to run natively in Linux environments, I recommend installing VirtualBox on your machine and using a Linux operating system as the host. Although it's possible to install Kubernetes on Windows, running the cluster from Linux optimizes performance and hardware usage.

Prerequisites:

  • A computer with at least 8 GB of RAM (recommended) to support multiple virtual machines.
  • An internet connection to download the necessary images.
  • Basic knowledge of handling the terminal in Linux.

Procedure:

Step A: Installing VirtualBox on Linux

Content:

  • Installing VirtualBox on Linux.
  • Basic VirtualBox configuration to create an optimal environment for Kubernetes.
    • [(Click here to continue with this step)] --> Under construction.

Step B: Installing and configuring the cluster's main node (Master)

In this step, we’ll install a Kubernetes Master node, which will act as the brain of the cluster, managing task scheduling, network control, and the management of the PODS' state.

  • [(Click here to continue with this step)] --> Under construction.

Step C: Installing and configuring a worker node

A Kubernetes cluster is not complete without worker nodes. These are responsible for running the workloads deployed in the cluster. Here, I’ll show you how to add your first Worker node.

  • [(Click here to continue with this step)] --> Under construction.

Step D: Cloning a second worker node for high availability

To test high availability (HA) scenarios, we will clone a second Worker node. This will allow you to simulate failures and see how Kubernetes manages service continuity.

  • [(Click here to continue with this step)] --> Under construction.

Other alternative tools for local clusters, which we will develop soon:

  • Minikube: The most popular option for individual users.
  • Kind: Lightweight and fast for unit tests.
  • Docker Desktop: Native integration with Kubernetes.
  • Other options: MicroK8s, K3s, K0s, etc.

Comments

Post a Comment

Popular posts from this blog

Unveiling the "TOP" command: Analyze your system like a power user.

Image
  The output you're seeing in that screenshot corresponds to the top command, which displays a real-time list of processes and system resource usage in a tabular format. Let’s break down each of the columns so you can see how much information it provides in such a compact space: Detailed explanation, step by step: The top section of the top command output provides an overview of the system status. Here is the breakdown: System Header : top - 23 : 05 : 14 up 19 min , 1 user, load average: 0.66 , 0.40 , 0.16 top : The name of the command. 23:05:14 : The current time. up 19 min : How long the system has been running (in this case, 19 minutes). 1 user : The number of users currently logged into the system. load average: 0.66, 0.40, 0.16 : The system load averages (the number of processes waiting to use the CPU) over the last 1, 5, and 15 minutes. These values indicate how busy the CPU is. A value of 1.0 means the CPU is fully loaded (using all available cores). Tasks : Tasks: 40...
Read more

Must-know Docker commands for power users.

Image
  Container Management docker ps # Lists running containers docker ps -a # Lists all containers (including stopped ones) docker run [image] # Creates and runs a container based on an image docker start [id/name] # Starts a stopped container docker stop [id/name] # Stops a running container docker restart [id/name] # Restarts a container docker rm [id/name] # Removes a stopped container docker exec -it [id/name] /bin/sh # Runs a command inside a container docker logs [id/name] # Shows the logs of a container docker inspect [id/name] # Shows details of a container docker port [id/name] # Shows the ports assigned to a container docker stats [id/name] # Displays resource usage statistics for containers docker top [id/name] # Shows running processes inside a container Image Management docker images # Lists available images locally docker pull [image] # Downloads an image from a repository docker rmi [image] # Removes a local image docker build -t [image-name] . # Builds...
Read more

How to Install Stable Diffusion on Windows

Image
  Introduction: Yes, it is possible to install Stable Diffusion on Windows, and here I will show you how to do it step by step. Before starting, it's important to mention that the main challenge for many users can be the hardware. While an NVIDIA RTX 3050 with 4 GB may be sufficient to get started, it is ideal to have an RTX 3060 with 12 GB or even a 3070 for better results and processing times. In this tutorial, I will guide you through the installation of Stable Diffusion using the most popular method: Automatic1111 Web UI, a user-friendly graphical interface for those who want to experiment with Stable Diffusion locally on their Windows PC. Prerequisites: Windows 10 or higher NVIDIA GPU (recommended to leverage CUDA acceleration) Updated GPU drivers Step 1: Install Python and Git Install Python 3.10.6 (not version 3.12): Visit the official Python website and download version 3.10.6. During the installation, make sure to select the "Add Python to PATH" option. This wil...
Read more