fix(node-baseline): pin the OIDC issuer to the Gateway VIP on prod nodes
gate / gate (pull_request) Successful in 1m46s
gate / conformance (pull_request) Has been skipped

After public DNS moved to the WAN IP (#40), prod nodes resolve
keycloak.home.keithjackson.dev to a WAN address the router does not
hairpin, so the apiserver could not reach its OIDC issuer. Adds an opt-in
node_baseline_hosts_pins /etc/hosts block; prod pins keycloak to
GATEWAY_VIP.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
jakman85andClaude Opus 5.5 committed 2026-10-03 17:39:37 -05:00
1 parent 576e1abb19
commit 788eaeae62
4 files changed
+89 -11

No files matched your search

@@ -1090,3 +1090,22 @@
{% endif %}
when: node_baseline_dns_mechanism == 'resolv-conf-file'
tags: [dns]
# /etc/hosts pins — tag `dns` (and `hosts` on its own). Some node processes must reach a
# public hostname at the in-cluster Gateway, not at its public answer. On prod, the
# kube-apiserver's OIDC issuer resolves publicly to the WAN IP, which the router does not
# hairpin. glibc reads /etc/hosts before any nameserver (nsswitch `files dns`), so a pin wins
# regardless of which resolver mechanism above is in effect. One marked block: entries
# dropped from node_baseline_hosts_pins disappear from the node, and an empty list
# removes the block.
- name: Pin node-process hostnames in /etc/hosts
ansible.builtin.blockinfile:
path: /etc/hosts
marker: "# {mark} node_baseline hosts pins (Ansible, tags: hosts)"
block: |
{% for pin in node_baseline_hosts_pins %}
{{ pin.ip }} {{ pin.names | join(' ') }}
{% endfor %}
state: "{{ 'present' if node_baseline_hosts_pins | length > 0 else 'absent' }}"
backup: true
tags: [dns, hosts]