basicstack/stack.basicstack.de
2
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Change Stalwart externalTrafficPolicy to Cluster for multi-node LB

Browse source 
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 <noreply@paperclip.ing>
This commit is contained in:
CTO Agent 2026-07-25 09:35:16 +00:00
parent c6b14ff0bc
commit c0a1bcb673
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
apps/stalwart/stalwart-fresh-deployment.yaml
View file

@ -24,7 +24,7 @@ metadata:
namespace: stalwart namespace: stalwart
spec: spec:
type: LoadBalancer type: LoadBalancer
externalTrafficPolicy: Local externalTrafficPolicy: Cluster
selector: selector:
app: stalwart app: stalwart
ports: ports:
@ -45,7 +45,7 @@ metadata:
namespace: stalwart namespace: stalwart
spec: spec:
type: LoadBalancer type: LoadBalancer
externalTrafficPolicy: Local externalTrafficPolicy: Cluster
selector: selector:
app: stalwart app: stalwart
ports: ports: