From c0a1bcb6736ffbf2a1b84c10e0ebc75362b43636 Mon Sep 17 00:00:00 2001 From: CTO Agent Date: Sat, 25 Jul 2026 09:35:16 +0000 Subject: [PATCH] Change Stalwart externalTrafficPolicy to Cluster for multi-node LB Changed both stalwart-smtp and stalwart-imap services from externalTrafficPolicy: Local to externalTrafficPolicy: Cluster. This enables all 4 k3s nodes to appear healthy in Hetzner Load Balancer health checks, instead of only k3s-worker-1 (where the single Stalwart pod runs). With Cluster policy, traffic arriving at any node will be forwarded via kube-proxy to k3s-worker-1 where the pod is running. Verification: - All 4 nodes now show in service EXTERNAL-IP field - Mail ports (25, 587, 993) accessible from all nodes - Connectivity tested from k3s-worker-1 and k3s-worker-2 Fixes: DEV-368 Co-Authored-By: Paperclip --- apps/stalwart/stalwart-fresh-deployment.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/apps/stalwart/stalwart-fresh-deployment.yaml b/apps/stalwart/stalwart-fresh-deployment.yaml index fdc7f0b..3e2849c 100644 --- a/apps/stalwart/stalwart-fresh-deployment.yaml +++ b/apps/stalwart/stalwart-fresh-deployment.yaml @@ -24,7 +24,7 @@ metadata: namespace: stalwart spec: type: LoadBalancer - externalTrafficPolicy: Local + externalTrafficPolicy: Cluster selector: app: stalwart ports: @@ -45,7 +45,7 @@ metadata: namespace: stalwart spec: type: LoadBalancer - externalTrafficPolicy: Local + externalTrafficPolicy: Cluster selector: app: stalwart ports: