From 6517c2193737d7a65bff5e71b53570f23b3004e7 Mon Sep 17 00:00:00 2001 From: Ruben Hensen Date: Sat, 24 Oct 2026 00:08:19 +0200 Subject: [PATCH] mbgwp: remove the unused wordpress-external NodePort It selected pods of the old mbgwp-helm release, so since the move to the official chart it had no endpoints and only held node port 30989 open. --- mbgwp/local-svc.yaml | 13 ------------- 1 file changed, 13 deletions(-) delete mode 100644 mbgwp/local-svc.yaml diff --git a/mbgwp/local-svc.yaml b/mbgwp/local-svc.yaml deleted file mode 100644 index b4be629..0000000 --- a/mbgwp/local-svc.yaml +++ /dev/null @@ -1,13 +0,0 @@ -apiVersion: v1 -kind: Service -metadata: - name: wordpress-external -spec: - type: NodePort - ports: - - port: 8080 # The port the service exposes internally - targetPort: 8080 # The port on the pods to which this service forwards traffic - nodePort: 30989 # The port on each node to access this service (must be between 30000-32767) - selector: - app.kubernetes.io/name: wordpress # Selector to match your WordPress pods - app.kubernetes.io/instance: mbgwp-helm # This might need adjustment based on your helm release