feat(vpn): prod egress-gateway group — k3s-prod-3, singleton, opt-in only
`[vpn_egress_gateway_prod]` is a SEPARATE inventory group with its own vaulted credentials, not a second member of `[vpn_egress_gateway]`. That group is the default target of playbooks/vpn.egress.gateway.yml, so adding a prod host to it would mean a flagless `ansible-playbook playbooks/vpn.egress.gateway.yml` silently reconfigures a prod node's kill-switch datapath. Prod is reached only by asking for it, with `--list-hosts` first: -e vpn_egress_gateway_hosts=vpn_egress_gateway_prod --limit k3s-prod-3 Node 3 because node 1's SSD was replaced yesterday (least operational history) and node 2 carries the §0b memattr history. Exactly one node, forever: Cilium OSS picks "the first node in lexical ordering" among nodeSelector matches, so a labelled k3s-prod-1 would silently steal the gateway role — and the public egress IP — from k3s-prod-3, with no event and no alert. vault.yml is a verbatim copy of the dev group's CIPHERTEXT: same PIA account per the operator, and copying the encrypted blob means the plaintext was never decrypted to disk, through a shell, or into a transcript. The two files are now independent — rotating means re-encrypting both, which is the right behaviour for two environments. Also corrects a stale inventory note that claimed k3s-prod-3 has wlp1s0 up on 192.168.2.195. Re-verified before choosing it as the gateway, because a second live uplink in a kill-switch datapath is not a footnote: there is no wl* netdev on the node at all, no phy80211 device, the /etc/network/interfaces wlp1s0 stanza is commented out, 192.168.2.195 is assigned nowhere, and the only IPv4 addresses are lo and eno1 192.168.2.12. Nothing needed bringing down. Co-Authored-By: Claude Opus 5 <[email protected]>
This commit is contained in:
1 parent
6f698f59af
commit
60e3f09c67
4 files changed
+234
-9
No files matched your search
@@ -45,6 +45,34 @@ localhost ansible_connection=local
|
||||
[vpn_egress_gateway]
|
||||
k3s-dev-3
|
||||
|
||||
# PROD's egress-gateway node — a SEPARATE group on purpose (2026-09-12).
|
||||
#
|
||||
# It is NOT a member of [vpn_egress_gateway] above, and k3s-prod-3 must never be added
|
||||
# there: that group is the DEFAULT target of playbooks/vpn.egress.gateway.yml, so a
|
||||
# flagless `ansible-playbook playbooks/vpn.egress.gateway.yml` would then silently
|
||||
# reconfigure a prod node's kill-switch datapath. Prod is reached only by asking for it:
|
||||
#
|
||||
# ansible-playbook playbooks/vpn.egress.gateway.yml \
|
||||
# -e vpn_egress_gateway_hosts=vpn_egress_gateway_prod --limit k3s-prod-3
|
||||
#
|
||||
# (`--list-hosts` first, every time. The play's target var is
|
||||
# `vpn_egress_gateway_hosts`, NOT the cluster-wide `k3s_hosts`.)
|
||||
#
|
||||
# WHY NODE 3, AND WHY EXACTLY ONE:
|
||||
# * node 1's SSD was replaced 2026-09-11 and it has the least operational history;
|
||||
# * node 2 carries the §0b memattr history;
|
||||
# * node 3 has a single uplink (eno1 192.168.2.12 — its wireless is gone: no wl* netdev
|
||||
# exists, the /etc/network/interfaces wlp1s0 stanza is commented out, and the
|
||||
# 192.168.2.195 address the earlier note below claimed is NOT present. Verified
|
||||
# 2026-09-12) which is what a kill-switch datapath wants.
|
||||
# * LEXICAL ORDERING HAZARD: Cilium OSS picks "the first node in lexical ordering" when
|
||||
# several match the policy's nodeSelector, so labelling k3s-prod-1 would SILENTLY take
|
||||
# the gateway role from k3s-prod-3. Exactly one host here, forever.
|
||||
# Its PIA credentials are its own vaulted group_vars/vpn_egress_gateway_prod/vault.yml —
|
||||
# the dev group's vault does not apply to a prod host.
|
||||
[vpn_egress_gateway_prod]
|
||||
k3s-prod-3
|
||||
|
||||
# The Proxmox HYPERVISOR host itself (NOT a k3s node) — target of playbooks/backup-s3.yml,
|
||||
# which stands up the off-cluster versitygw S3 backup target for Velero + CNPG. Reached DIRECTLY
|
||||
# over SSH as root (its own 192.168.2.102:22, the pfSense NAT to the host's 192.168.1.9), so
|
||||
@@ -116,8 +144,13 @@ k3s-prod-1 ansible_host=192.168.2.10 ansible_port=22 k3s_node_ip=192.168.2.10
|
||||
# needs the same >= 6.13 kernel. Its disk is a THIRD distinct model (WDC WDS500G2B0A SATA
|
||||
# SSD) — all three nodes differ on disk, so the §2 Longhorn/etcd symmetry gap is now
|
||||
# three-way, not a node-1 outlier.
|
||||
# NOTE: node 3 also has wlp1s0 up on 192.168.2.195 (wifi). `ansible_host` is deliberately
|
||||
# the WIRED eno1 address — the same directly-routable 192.168.2.x LAN as nodes 1 and 2.
|
||||
# NOTE (CORRECTED 2026-09-12): this used to read "node 3 also has wlp1s0 up on
|
||||
# 192.168.2.195 (wifi)". It does not — re-verified before making node 3 the VPN egress
|
||||
# gateway, because a second live uplink in a kill-switch datapath is not a detail: there is
|
||||
# NO wl* netdev on the node at all, no phy80211 device, the wlp1s0 stanza in
|
||||
# /etc/network/interfaces is commented out, 192.168.2.195 is assigned nowhere, and the only
|
||||
# IPv4 addresses are lo and eno1 192.168.2.12. `ansible_host` is that WIRED eno1 address —
|
||||
# the same directly-routable 192.168.2.x LAN as nodes 1 and 2.
|
||||
k3s-prod-3 ansible_host=192.168.2.12 ansible_port=22 k3s_node_ip=192.168.2.12
|
||||
|
||||
# Umbrella group group_vars/k3s_prod/ attaches to (mirrors dev's [k3s_servers:children]
|
||||
|
||||
Reference in new issue
Block a user