Vezpi/Blog
1
0
Fork 0
Code Issues Pull Requests Actions Wiki Activity

Auto-update blog content from Obsidian: 2025-07-18 21:18:35
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 6s
Details
Blog Deployment / Build (push) Has been skipped
Details
Blog Deployment / Deploy-Staging (push) Successful in 10s
Details
Blog Deployment / Test-Staging (push) Successful in 3s
Details
Blog Deployment / Merge (push) Successful in 6s
Details
Blog Deployment / Deploy-Production (push) Successful in 9s
Details
Blog Deployment / Test-Production (push) Successful in 3s
Details
Blog Deployment / Clean (push) Has been skipped
Details
Blog Deployment / Notify (push) Successful in 2s
Details

Browse Source
This commit is contained in:
Gitea Actions
2025-07-18 21:18:35 +00:00
parent f6b4affd1e
commit f861acac7f
2 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
content/post/8-create-manual-kubernetes-cluster-kubeadm.fr.md
View File

@@ -6,7 +6,6 @@ date: 2025-07-18
draft: false
tags:
- kubernetes
- highly-available
- kubeadm
categories:
- homelab
@@ -187,7 +186,7 @@ sudo apt-mark hold kubectl
Une fois tous les nœuds préparés, on peut initialiser le **plan de contrôle** Kubernetes sur le **premier nœud master**.
### Initialisation
### Amorcer le Cluster
Exécutez la commande suivante pour amorcer le cluster:
```bash