ivanch/blog.ivanch.me
1
0
Fork 0
mirror of https://github.com/ivanch/blog.ivanch.me.git synced 2026-02-14 10:18:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

note about talos

Browse Source
This commit is contained in:
José Henrique
2026-02-10 20:54:11 -03:00
parent 73e36fdfbc
commit 020001b2e9
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
content/posts/home-k8s.md
View File

@@ -14,6 +14,8 @@ As you may or may not know, k8s is a container orchestration platform that autom
Currently I'm running them while all config files are on a NFS server, this makes managing configurations easier and backup-ready. For this, I'm using `nfs-subdir-external-provisioner` to manage PVCs through NFS. I have also setup 2 backup cronjobs: one for local servers and another for a remote server. Currently I'm running them while all config files are on a NFS server, this makes managing configurations easier and backup-ready. For this, I'm using `nfs-subdir-external-provisioner` to manage PVCs through NFS. I have also setup 2 backup cronjobs: one for local servers and another for a remote server.
Note: I may look into Talos Linux in the future, but for now I'm happy with k3s.
## Pros and cons ## Pros and cons
Pros that I have noticed: Pros that I have noticed:
@@ -24,7 +26,7 @@ Pros that I have noticed:
* **Backups** are easy to manage if you have all configurations under one place. * **Backups** are easy to manage if you have all configurations under one place.
* **Cronjobs** are a breeze to set up and manage, mainly if you need to perform backup rituals. * **Cronjobs** are a breeze to set up and manage, mainly if you need to perform backup rituals.
* **"Enterprise-grade"** cluster in your home! * **"Enterprise-grade"** cluster in your home!
* **Have fun :)** * **It's fun :)**
Cons: Cons:
* **Complexity**: While k3s simplifies many aspects of Kubernetes, it still requires a certain level of understanding of container orchestration concepts. * **Complexity**: While k3s simplifies many aspects of Kubernetes, it still requires a certain level of understanding of container orchestration concepts.
@@ -36,11 +38,11 @@ Cons:
This is my current (might be outdated) setup: This is my current (might be outdated) setup:
* 2 Orange Pi running k3s * 2 Orange Pi running k3s
- Each with 4 GB RAM, 4C/4T, 256GB SD card on each. - Each with 4 GB RAM, 4C/4T
* 1 Mini PC * 1 Mini PC
- 6 GB RAM, 2C/4T, 64GB internal memory + 512GB SD Card - 6 GB RAM, 2C/4T
* Proxmox * Proxmox
- 32 GB RAM, 6C/12T, 1 TB SSD - 32 GB RAM, 6C/12T
- Currently I run these VMs with k3s: - Currently I run these VMs with k3s:
- 1 prod-like VM - 1 prod-like VM
- 1 dev-like VM - 1 dev-like VM