Fix etcd advertised WAN ports: 61379/61380, not 12379/12380

The chosen ports (12379/12380) actually fell inside the existing
GameServer port-forward's range (4000-50000) on the UniFi router,
confirmed live when creating the rule ('Port 12379 conflicts with port
4000-50000 used by GameServer'). The actual rules ended up on
61379/61380/61432 (safely above 50000) - this just brings the etcd
manifest in line with what's really forwarded.
This commit is contained in:
Scooby Husky
2026-08-19 00:01:31 -05:00
parent c2f0f38012
commit a3e0ae3427
@@ -68,10 +68,10 @@ spec:
- --name=home - --name=home
- --data-dir=/var/lib/etcd/data - --data-dir=/var/lib/etcd/data
- --listen-client-urls=http://0.0.0.0:2379 - --listen-client-urls=http://0.0.0.0:2379
- --advertise-client-urls=http://home.kube.huskypup.net:12379 - --advertise-client-urls=http://home.kube.huskypup.net:61379
- --listen-peer-urls=http://0.0.0.0:2380 - --listen-peer-urls=http://0.0.0.0:2380
- --initial-advertise-peer-urls=http://home.kube.huskypup.net:12380 - --initial-advertise-peer-urls=http://home.kube.huskypup.net:61380
- --initial-cluster=home=http://home.kube.huskypup.net:12380,vps=http://100.108.113.41:2380,witness=http://100.108.130.74:2380 - --initial-cluster=home=http://home.kube.huskypup.net:61380,vps=http://100.108.113.41:2380,witness=http://100.108.130.74:2380
- --initial-cluster-state=new - --initial-cluster-state=new
- --initial-cluster-token=ha-failover-quorum - --initial-cluster-token=ha-failover-quorum
ports: ports: