diff options
| author | Paul Buetow <paul@buetow.org> | 2025-07-20 09:07:55 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2025-07-20 09:07:55 +0300 |
| commit | b743f2d9849626c5affd6839dfa04b6bccd9f7b7 (patch) | |
| tree | d195176ed7e80ce221e0c19bbb25810694fb0f57 /gemfeed | |
| parent | 236ea2357557d10d8b6084d0bb8d059d85408f26 (diff) | |
Update content for md
Diffstat (limited to 'gemfeed')
| -rw-r--r-- | gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.md b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.md index 151f5bee..a380225c 100644 --- a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.md +++ b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.md @@ -59,7 +59,7 @@ This is the sixth blog post about the f3s series for self-hosting demands in a h ## Introduction -In the previous posts, we set up a FreeBSD-based Kubernetes cluster using k3s. While the base system works well, Kubernetes workloads often require persistent storage for databases, configuration files, and application data. Local storage on each node has significant limitations: +In the previous posts, we set up a WireGuard mesh network. In the future, we will also setting up a Kubernetes cluster. Kubernetes workloads often require persistent storage for databases, configuration files, and application data. Local storage on each node has significant limitations: * No data sharing: Pods (once we run Kubernetes) on different nodes can't access the same data * Pod mobility: If a pod moves to another node, it loses access to its data |