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

Auto-update blog content from Obsidian: 2025-05-18 20:13:27
All checks were successful
Deploy / Deploy (push) Successful in 3s
Details

Browse Source
This commit is contained in:
Gitea Actions 2025-05-18 20:13:27 +00:00
parent d6a38da3f1
commit d86efc2296
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
content/page/homelab/index.md
View File

@ -123,9 +123,16 @@ Here what is look like
With the hardware foundation set, the next step was to decide what software would orchestrate everything, the real engine behind every experiment, deployment, and learning opportunity. With the hardware foundation set, the next step was to decide what software would orchestrate everything, the real engine behind every experiment, deployment, and learning opportunity.
### Hypervisor ### Hypervisor
At the basement we have the hypervisor, in that case this is Proxmox VE 8 which I'm currently using. It's pretty good for a small cluster, it provides live migration, HA and integrates Ceph out of the box At the groud level, I'm using 3-nodes Proxmox VE 8 cluster, a KVM based hypervisor which can also manage LXC. The OS is based on Debian, it provides live migration, HA and integrates Ceph out of the box.
### Virtual Machines
For the moment, I'm mainly use only one virtual machine along with one LXC. The former is basically a clone of my old physical server, where the most part of my applications are running as Docker containers, the latter is a simple jump server.
### Network ### Network
### Storage
### Application ### Application
#### Docker #### Docker
#### Kubernetes #### Kubernetes