From 95bccdde08352b21d4f15728ca957a2294a3c665 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 5 Feb 2026 21:13:10 +0200 Subject: Update content for gemtext --- ...25-10-02-f3s-kubernetes-with-freebsd-part-7.gmi | 20 ++++++++++---------- ...0-02-f3s-kubernetes-with-freebsd-part-7.gmi.tpl | 20 ++++++++++---------- gemfeed/atom.xml | 22 +++++++++++----------- 3 files changed, 31 insertions(+), 31 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.gmi b/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.gmi index 45b17dd7..afae2c42 100644 --- a/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.gmi +++ b/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.gmi @@ -948,15 +948,15 @@ Repeat the same configuration on f1. Both hosts will run `relayd` listening on t *Adding LAN ingress to services*: -To expose a service on the LAN, add a second Ingress resource to its Helm chart. Here's an example for Navidrome: +To expose a service on the LAN, add a second Ingress resource to its Helm chart. Here's an example: ```yaml --- -# LAN Ingress for navidrome.f3s.lan.foo.zone +# LAN Ingress for f3s.lan.foo.zone apiVersion: networking.k8s.io/v1 kind: Ingress metadata: - name: navidrome-ingress-lan + name: ingress-lan namespace: services annotations: spec.ingressClassName: traefik @@ -964,17 +964,17 @@ metadata: spec: tls: - hosts: - - navidrome.f3s.lan.foo.zone + - f3s.lan.foo.zone secretName: f3s-lan-tls rules: - - host: navidrome.f3s.lan.foo.zone + - host: f3s.lan.foo.zone http: paths: - path: / pathType: Prefix backend: service: - name: navidrome-service + name: service port: number: 4533 ``` @@ -989,10 +989,10 @@ Key points: Apply the ingress and test: ```sh -$ kubectl apply -f navidrome-ingress-lan.yaml -ingress.networking.k8s.io/navidrome-ingress-lan created +$ kubectl apply -f ingress-lan.yaml +ingress.networking.k8s.io/ingress-lan created -$ curl -k https://navidrome.f3s.lan.foo.zone +$ curl -k https://f3s.lan.foo.zone HTTP/2 302 location: /app/ ``` @@ -1006,7 +1006,7 @@ Add DNS entries to `/etc/hosts` on your laptop: ```sh $ sudo tee -a /etc/hosts << 'EOF' # f3s LAN services -192.168.1.138 navidrome.f3s.lan.foo.zone +192.168.1.138 f3s.lan.foo.zone EOF ``` diff --git a/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.gmi.tpl b/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.gmi.tpl index 9c715877..d8633448 100644 --- a/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.gmi.tpl +++ b/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.gmi.tpl @@ -913,15 +913,15 @@ Repeat the same configuration on f1. Both hosts will run `relayd` listening on t *Adding LAN ingress to services*: -To expose a service on the LAN, add a second Ingress resource to its Helm chart. Here's an example for Navidrome: +To expose a service on the LAN, add a second Ingress resource to its Helm chart. Here's an example: ```yaml --- -# LAN Ingress for navidrome.f3s.lan.foo.zone +# LAN Ingress for f3s.lan.foo.zone apiVersion: networking.k8s.io/v1 kind: Ingress metadata: - name: navidrome-ingress-lan + name: ingress-lan namespace: services annotations: spec.ingressClassName: traefik @@ -929,17 +929,17 @@ metadata: spec: tls: - hosts: - - navidrome.f3s.lan.foo.zone + - f3s.lan.foo.zone secretName: f3s-lan-tls rules: - - host: navidrome.f3s.lan.foo.zone + - host: f3s.lan.foo.zone http: paths: - path: / pathType: Prefix backend: service: - name: navidrome-service + name: service port: number: 4533 ``` @@ -954,10 +954,10 @@ Key points: Apply the ingress and test: ```sh -$ kubectl apply -f navidrome-ingress-lan.yaml -ingress.networking.k8s.io/navidrome-ingress-lan created +$ kubectl apply -f ingress-lan.yaml +ingress.networking.k8s.io/ingress-lan created -$ curl -k https://navidrome.f3s.lan.foo.zone +$ curl -k https://f3s.lan.foo.zone HTTP/2 302 location: /app/ ``` @@ -971,7 +971,7 @@ Add DNS entries to `/etc/hosts` on your laptop: ```sh $ sudo tee -a /etc/hosts << 'EOF' # f3s LAN services -192.168.1.138 navidrome.f3s.lan.foo.zone +192.168.1.138 f3s.lan.foo.zone EOF ``` diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 2afb3638..ef2b4d5e 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2026-02-05T17:48:12+02:00 + 2026-02-05T21:12:19+02:00 foo.zone feed To be in the .zone! @@ -5397,15 +5397,15 @@ _relayd relayd 2903 12 *Adding LAN ingress to services*:

-To expose a service on the LAN, add a second Ingress resource to its Helm chart. Here's an example for Navidrome:
+To expose a service on the LAN, add a second Ingress resource to its Helm chart. Here's an example:

 ---
-# LAN Ingress for navidrome.f3s.lan.foo.zone
+# LAN Ingress for f3s.lan.foo.zone
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
-  name: navidrome-ingress-lan
+  name: ingress-lan
   namespace: services
   annotations:
     spec.ingressClassName: traefik
@@ -5413,17 +5413,17 @@ metadata:
 spec:
   tls:
     - hosts:
-        - navidrome.f3s.lan.foo.zone
+        - f3s.lan.foo.zone
       secretName: f3s-lan-tls
   rules:
-    - host: navidrome.f3s.lan.foo.zone
+    - host: f3s.lan.foo.zone
       http:
         paths:
           - path: /
             pathType: Prefix
             backend:
               service:
-                name: navidrome-service
+                name: service
                 port:
                   number: 4533
@@ -5442,10 +5442,10 @@ spec: by Lorenzo Bettini http://www.lorenzobettini.it http://www.gnu.org/software/src-highlite --> -
$ kubectl apply -f navidrome-ingress-lan.yaml
-ingress.networking.k8s.io/navidrome-ingress-lan created
+
$ kubectl apply -f ingress-lan.yaml
+ingress.networking.k8s.io/ingress-lan created
 
-$ curl -k https://navidrome.f3s.lan.foo.zone
+$ curl -k https://f3s.lan.foo.zone
 HTTP/2 302 
 location: /app/
 

@@ -5462,7 +5462,7 @@ http://www.lorenzobettini.it
 http://www.gnu.org/software/src-highlite -->
 
$ sudo tee -a /etc/hosts << 'EOF'
 # f3s LAN services
-192.168.1.138  navidrome.f3s.lan.foo.zone
+192.168.1.138  f3s.lan.foo.zone
 EOF
 

 

-- 
cgit v1.2.3