diff options
| author | Paul Buetow <paul@buetow.org> | 2025-07-13 16:57:11 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2025-07-13 16:57:11 +0300 |
| commit | 1966574e65d7558e354e16e1e8212d7637e9533f (patch) | |
| tree | 1ab8db03ebe7cb43e695bbbe976f7bbd3f489036 /gemfeed | |
| parent | 2196a00cfefc7cdb1cd110d4cba1b67c8d2fc2bd (diff) | |
Update content for html
Diffstat (limited to 'gemfeed')
| -rw-r--r-- | gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html | 3 | ||||
| -rw-r--r-- | gemfeed/atom.xml | 5 |
2 files changed, 5 insertions, 3 deletions
diff --git a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html index 4cb061bd..a1830ef9 100644 --- a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html +++ b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html @@ -1794,7 +1794,8 @@ Jul <font color="#000000">06</font> <font color="#000000">10</font>:<font color= <li>Flexible redundancy: Configure different replication levels per directory or file, optimising storage efficiency.</li> <li>FreeBSD support: MooseFS has native FreeBSD support, making it a natural fit for the f3s project.</li> </ul><br /> -<span>Both technologies could run on top of our encrypted ZFS volumes, combining ZFS's data integrity and encryption features with distributed storage capabilities. This would be particularly interesting for workloads that need either S3-compatible APIs (MinIO) or transparent distributed POSIX storage (MooseFS).</span><br /> +<span>Both technologies could run on top of our encrypted ZFS volumes, combining ZFS's data integrity and encryption features with distributed storage capabilities. This would be particularly interesting for workloads that need either S3-compatible APIs (MinIO) or transparent distributed POSIX storage (MooseFS). What about Ceph and GlusterFS? Unfortunately, there doesn't seem to be great native FreeBSD support for them. However, other alternatives also appear suitable for my use case.</span><br /> +<br /> <br /> <span>I'm looking forward to the next post in this series, where we will set up k3s (Kubernetes) on the Linux VMs.</span><br /> <br /> diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 5488b4e1..adcfa57e 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"> - <updated>2025-07-13T16:50:30+03:00</updated> + <updated>2025-07-13T16:55:45+03:00</updated> <title>foo.zone feed</title> <subtitle>To be in the .zone!</subtitle> <link href="https://foo.zone/gemfeed/atom.xml" rel="self" /> @@ -1801,7 +1801,8 @@ Jul <font color="#000000">06</font> <font color="#000000">10</font>:<font color= <li>Flexible redundancy: Configure different replication levels per directory or file, optimising storage efficiency.</li> <li>FreeBSD support: MooseFS has native FreeBSD support, making it a natural fit for the f3s project.</li> </ul><br /> -<span>Both technologies could run on top of our encrypted ZFS volumes, combining ZFS's data integrity and encryption features with distributed storage capabilities. This would be particularly interesting for workloads that need either S3-compatible APIs (MinIO) or transparent distributed POSIX storage (MooseFS).</span><br /> +<span>Both technologies could run on top of our encrypted ZFS volumes, combining ZFS's data integrity and encryption features with distributed storage capabilities. This would be particularly interesting for workloads that need either S3-compatible APIs (MinIO) or transparent distributed POSIX storage (MooseFS). What about Ceph and GlusterFS? Unfortunately, there doesn't seem to be great native FreeBSD support for them. However, other alternatives also appear suitable for my use case.</span><br /> +<br /> <br /> <span>I'm looking forward to the next post in this series, where we will set up k3s (Kubernetes) on the Linux VMs.</span><br /> <br /> |