Auto-update blog content from Obsidian: 2025-07-18 14:37:16
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 5s
Blog Deployment / Build (push) Has been skipped
Blog Deployment / Deploy-Staging (push) Successful in 10s
Blog Deployment / Test-Staging (push) Successful in 2s
Blog Deployment / Merge (push) Successful in 6s
Blog Deployment / Deploy-Production (push) Successful in 9s
Blog Deployment / Test-Production (push) Successful in 2s
Blog Deployment / Clean (push) Has been skipped
Blog Deployment / Notify (push) Successful in 2s
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 5s
Blog Deployment / Build (push) Has been skipped
Blog Deployment / Deploy-Staging (push) Successful in 10s
Blog Deployment / Test-Staging (push) Successful in 2s
Blog Deployment / Merge (push) Successful in 6s
Blog Deployment / Deploy-Production (push) Successful in 9s
Blog Deployment / Test-Production (push) Successful in 2s
Blog Deployment / Clean (push) Has been skipped
Blog Deployment / Notify (push) Successful in 2s
This commit is contained in:
@@ -1,11 +1,15 @@
|
|||||||
---
|
---
|
||||||
slug: create-manual-kubernetes-cluster-kubeadm
|
slug: create-manual-kubernetes-cluster-kubeadm
|
||||||
title: Template
|
title: Créer un Cluster Kubernetes Hautement Disponible avec kubeadm sur des VMs
|
||||||
description:
|
description: Guide étape par étape pour créer manuellement un cluster Kubernetes hautement disponible sur des machines virtuelles avec kubeadm.
|
||||||
date:
|
date: 2025-07-18
|
||||||
draft: true
|
draft: true
|
||||||
tags:
|
tags:
|
||||||
|
- kubernetes
|
||||||
|
- highly-available
|
||||||
|
- kubeadm
|
||||||
categories:
|
categories:
|
||||||
|
- homelab
|
||||||
---
|
---
|
||||||
|
|
||||||
## Intro
|
## Intro
|
||||||
@@ -615,21 +619,21 @@ __ [cilium-test-1] All 73 tests (739 actions) successful, 50 tests skipped, 1 sc
|
|||||||
|
|
||||||
⌛ Ce test de connectivité peut prendre jusqu’à **30 minutes**.
|
⌛ Ce test de connectivité peut prendre jusqu’à **30 minutes**.
|
||||||
|
|
||||||
## Deploying a Sample Application
|
---
|
||||||
|
|
||||||
Creating a simple Deployment and Service
|
|
||||||
|
|
||||||
Exposing it via NodePort or LoadBalancer
|
|
||||||
|
|
||||||
Verifying functionality
|
|
||||||
|
|
||||||
## Conclusion
|
## Conclusion
|
||||||
|
|
||||||
Summary of the steps
|
Dans cet article, nous avons vu comment **créer manuellement un cluster Kubernetes** à l’aide de `kubeadm`, sur un ensemble de 6 machines Ubuntu (3 masters et 3 workers) préalablement déployées avec Terraform sur Proxmox.
|
||||||
|
|
||||||
When to use this manual method
|
Nous avons suivi les étapes suivantes :
|
||||||
|
- Préparation des nœuds avec les outils, modules noyau et runtime nécessaires
|
||||||
|
- Installation des paquets Kubernetes
|
||||||
|
- Initialisation du cluster depuis le premier nœud master
|
||||||
|
- Ajout des autres nœuds du plan de contrôle et les workers
|
||||||
|
- Vérification de l’état et du bon fonctionnement du cluster
|
||||||
|
|
||||||
|
Cette approche manuelle permet de mieux comprendre comment un cluster Kubernetes est construit en interne. C’est une excellente base avant de passer à l’automatisation dans les prochains articles, en utilisant des outils comme Ansible.
|
||||||
|
|
||||||
|
Restez connectés, la suite sera axée sur l’automatisation de tout ça !
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@@ -1,11 +1,15 @@
|
|||||||
---
|
---
|
||||||
slug: create-manual-kubernetes-cluster-kubeadm
|
slug: create-manual-kubernetes-cluster-kubeadm
|
||||||
title: Template
|
title: Create a Highly Available Kubernetes Cluster with kubeadm on VMs
|
||||||
description:
|
description: Step-by-step guide to manually build a highly available Kubernetes cluster on virtual machines using kubeadm
|
||||||
date:
|
date: 2025-07-18
|
||||||
draft: true
|
draft: true
|
||||||
tags:
|
tags:
|
||||||
|
- kubernetes
|
||||||
|
- highly-available
|
||||||
|
- kubeadm
|
||||||
categories:
|
categories:
|
||||||
|
- homelab
|
||||||
---
|
---
|
||||||
|
|
||||||
## Intro
|
## Intro
|
||||||
@@ -612,18 +616,20 @@ __ [cilium-test-1] All 73 tests (739 actions) successful, 50 tests skipped, 1 sc
|
|||||||
|
|
||||||
⌛This connectivity test could take up to 30 minutes.
|
⌛This connectivity test could take up to 30 minutes.
|
||||||
|
|
||||||
## Deploying a Sample Application
|
---
|
||||||
|
|
||||||
Creating a simple Deployment and Service
|
|
||||||
|
|
||||||
Exposing it via NodePort or LoadBalancer
|
|
||||||
|
|
||||||
Verifying functionality
|
|
||||||
|
|
||||||
## Conclusion
|
## Conclusion
|
||||||
|
|
||||||
Summary of the steps
|
In this post, we walked through the **manual creation of a Kubernetes cluster** using `kubeadm`, on top of 6 Ubuntu VMs (3 masters and 3 workers) previously provisioned with Terraform on Proxmox.
|
||||||
|
|
||||||
When to use this manual method
|
We went step by step:
|
||||||
|
- Preparing the nodes with the required tools, kernel modules, and container runtime
|
||||||
|
- Installing the Kubernetes packages
|
||||||
|
- Bootstrapping the cluster from the first master node
|
||||||
|
- Joining additional control-plane and worker nodes
|
||||||
|
- Verifying that the cluster is healthy and ready
|
||||||
|
|
||||||
|
This manual approach helps to demystify how Kubernetes clusters are built behind the scenes. It’s a solid foundation before automating the process in future posts using tools like Ansible.
|
||||||
|
|
||||||
|
Stay tuned, next time we’ll look into automating all of this!
|
||||||
|
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user