diff options
| author | Paul Buetow <paul@buetow.org> | 2025-07-13 16:51:48 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2025-07-13 16:51:48 +0300 |
| commit | 947b7154dd21a2934e152e25fb7d90e8c1b36bce (patch) | |
| tree | 7ef1d734a4b74dc33410f03d20d9048879c2f80a /gemfeed | |
| parent | ec274d473332eceb14f626a56907404c42e9f971 (diff) | |
Update content for md
Diffstat (limited to 'gemfeed')
| -rw-r--r-- | gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.md | 4 |
1 files changed, 2 insertions, 2 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 87a4f63c..51742ccb 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 @@ -47,7 +47,7 @@ This is the sixth blog post about the f3s series for self-hosting demands in a h * [⇢ ⇢ ⇢ CARP Control Script for Clean Failover](#carp-control-script-for-clean-failover) * [⇢ ⇢ ⇢ CARP Management Script](#carp-management-script) * [⇢ ⇢ ⇢ Automatic Failback After Reboot](#automatic-failback-after-reboot) -* [⇢ ⇢ Client Configuration for Stunnel](#client-configuration-for-stunnel) +* [⇢ ⇢ Client Configuration for NFS via Stunnel](#client-configuration-for-nfs-via-stunnel) * [⇢ ⇢ ⇢ Configuring Rocky Linux Clients (`r0`, `r1`, `r2`)](#configuring-rocky-linux-clients-r0-r1-r2) * [⇢ ⇢ ⇢ Testing NFS Mount with Stunnel](#testing-nfs-mount-with-stunnel) * [⇢ ⇢ ⇢ Testing CARP Failover with mounted clients and stale file handles:](#testing-carp-failover-with-mounted-clients-and-stale-file-handles) @@ -1311,7 +1311,7 @@ So, in summary: This ensures `f0` automatically resumes its role as primary storage server after any reboot, while providing administrative control when needed. -## Client Configuration for Stunnel +## Client Configuration for NFS via Stunnel To mount NFS shares with stunnel encryption, clients must install and configure stunnel using their client certificates. |