stabify/infrastructure
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

added k3s planning md changes

Browse Source
This commit is contained in:
Nick Adam
2026-01-19 00:05:20 +01:00
parent 48fa532b82
commit 4e1f015a49
9 changed files with 6 additions and 117 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
K3S_PLANNING.md
View File

@@ -10,7 +10,7 @@ We will deploy a High-Availability (HA) K3s cluster consisting of 3 Control Plan
* VLAN 40 (IP Range: `10.100.40.0/24`).
* **VIP (Virtual IP):** A floating IP managed by `kube-vip` for the API Server and Ingress Controller.
* **Ingress Flow:**
* `Internet` -> `Traefik Edge (VM 302)` -> `K3s VIP (LoadBalancer)` -> `Traefik Ingress (K3s)` -> `Pod`.
* `Internet` -> `Traefik im k3s Cluster (VIP 10.100.40.6)` -> `Traefik Ingress (K3s)` -> `Pod`.
* **GitOps:**
* **Tool:** FluxCD.
* **Repository Structure:**
@@ -61,10 +61,11 @@ We will create a new role `k3s` and a corresponding playbook.
* `k3s-api.stabify.de` -> `10.100.40.5` (VIP).
* `*.k3s.stabify.de` -> `10.100.40.6` (Ingress VIP).
* **Traefik Edge Config (`vm-docker-traefik-302`):**
* New Router/Service in `config/dynamic/30-k3s.yaml`.
* Rule: `HostRegexp('^.+\.k3s\.stabify\.de$')`
* Target: `https://10.100.40.6:443` (PassHostHeader=true).
* **Traefik Edge Config (im k3s Cluster):**
* File Provider für TLS Passthrough zu k3s Services.
* ConfigMap: `traefik-edge-dynamic-k3s`
* Rule: `HostSNIRegexp('^.+\.k3s\.stabify\.de$')`
* Target: `10.100.40.6:443` (TLS Passthrough).
## 5. Next Steps for Implementation