Drop the nas.rubenhensen.nl and alv.rubenhensen.nl ingresses

Neither host has a DNS record, so both were unreachable and cert-manager
has been failing to renew their certificates since 6 April. DSM stays
reachable on the LAN at 192.168.1.99. The nas app only held that ingress
and its ExternalName service, so it goes entirely.
This commit is contained in:
Ruben Hensen committed 2026-10-22 09:36:26 +02:00
1 parent 1f736cd4c7
commit 8a66913a54
4 files changed
-107

No files matched your search

-29
View File
@@ -1,29 +0,0 @@
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: nas-ingress
annotations:
cert-manager.io/cluster-issuer: prod-cluster-issuer
nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
nginx.ingress.kubernetes.io/ssl-passthrough: "false"
spec:
ingressClassName: nginx
rules:
- host: nas.rubenhensen.nl
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: nas-external
port:
number: 5000
# TLS configuration for HTTPS
tls:
# TLS secretName used on ClusterIssuer
- secretName: letsencrypt-prod
hosts:
- nas.rubenhensen.nl
-14
View File
@@ -1,14 +0,0 @@
apiVersion: v1
kind: Service
metadata:
name: nas-external
spec:
type: ExternalName
externalName: 192.168.1.99
ports:
- name: nas-5000
protocol: TCP
port: 5000
- name: nas-5001
protocol: TCP
port: 5001