2026-01-15 16:29:32 -03:00
|
|
|
# infrastructure/core/coredns-custom.yaml
|
|
|
|
|
apiVersion: v1
|
|
|
|
|
kind: ConfigMap
|
|
|
|
|
metadata:
|
|
|
|
|
name: coredns-custom
|
|
|
|
|
namespace: kube-system
|
|
|
|
|
data:
|
|
|
|
|
bstein-dev.server: |
|
|
|
|
|
bstein.dev:53 {
|
|
|
|
|
errors
|
|
|
|
|
cache 30
|
|
|
|
|
hosts {
|
2026-08-08 17:59:45 -03:00
|
|
|
192.168.22.9 agent.hermes.bstein.dev
|
2026-01-17 08:16:57 -03:00
|
|
|
192.168.22.9 alerts.bstein.dev
|
|
|
|
|
192.168.22.9 auth.bstein.dev
|
|
|
|
|
192.168.22.9 bstein.dev
|
2026-01-17 08:05:33 -03:00
|
|
|
10.43.6.87 budget.bstein.dev
|
2026-01-17 08:16:57 -03:00
|
|
|
192.168.22.9 call.live.bstein.dev
|
|
|
|
|
192.168.22.9 cd.bstein.dev
|
|
|
|
|
192.168.22.9 chat.ai.bstein.dev
|
2026-08-21 06:43:18 +00:00
|
|
|
192.168.22.9 chat.bstein.dev
|
2026-01-17 08:16:57 -03:00
|
|
|
192.168.22.9 ci.bstein.dev
|
|
|
|
|
192.168.22.9 cloud.bstein.dev
|
|
|
|
|
192.168.22.9 health.bstein.dev
|
|
|
|
|
192.168.22.9 kit.live.bstein.dev
|
|
|
|
|
192.168.22.9 live.bstein.dev
|
|
|
|
|
192.168.22.9 logs.bstein.dev
|
|
|
|
|
192.168.22.9 longhorn.bstein.dev
|
2026-01-18 08:12:06 -03:00
|
|
|
192.168.22.4 mail.bstein.dev
|
2026-01-17 08:16:57 -03:00
|
|
|
192.168.22.9 matrix.live.bstein.dev
|
|
|
|
|
192.168.22.9 metrics.bstein.dev
|
|
|
|
|
192.168.22.9 monero.bstein.dev
|
2026-05-21 03:30:32 -03:00
|
|
|
192.168.22.9 moonlight.bstein.dev
|
2026-01-17 08:05:33 -03:00
|
|
|
10.43.6.87 money.bstein.dev
|
2026-01-17 08:16:57 -03:00
|
|
|
192.168.22.9 notes.bstein.dev
|
|
|
|
|
192.168.22.9 office.bstein.dev
|
|
|
|
|
192.168.22.9 pegasus.bstein.dev
|
2026-01-19 23:45:31 -03:00
|
|
|
3.136.224.193 pm-bounces.bstein.dev
|
|
|
|
|
3.150.68.49 pm-bounces.bstein.dev
|
|
|
|
|
18.189.137.81 pm-bounces.bstein.dev
|
2026-01-17 08:16:57 -03:00
|
|
|
192.168.22.9 registry.bstein.dev
|
|
|
|
|
192.168.22.9 scm.bstein.dev
|
|
|
|
|
192.168.22.9 secret.bstein.dev
|
|
|
|
|
192.168.22.9 sso.bstein.dev
|
|
|
|
|
192.168.22.9 stream.bstein.dev
|
2026-05-21 02:07:17 -03:00
|
|
|
192.168.22.9 wolf.bstein.dev
|
2026-01-17 08:16:57 -03:00
|
|
|
192.168.22.9 tasks.bstein.dev
|
2026-08-21 06:43:18 +00:00
|
|
|
192.168.22.9 triage.bstein.dev
|
2026-01-17 08:16:57 -03:00
|
|
|
192.168.22.9 vault.bstein.dev
|
refactor(hermes): rename the owner agent host to worker.bstein.dev
Introduce worker.bstein.dev as the canonical hostname for the owner-only
Hermes coordinator, previously agent.hermes.bstein.dev.
The old host is deliberately kept alive. CoreDNS, both agent Ingresses and
the hermes-sites certificate now serve BOTH names, so merging this cannot
take away the endpoint the operator uses to reach the coordinator. Retiring
agent.hermes.bstein.dev is a separate, separately scheduled change. No
redirect middleware is added.
What switches to the new host:
- HERMES_DASHBOARD_PUBLIC_URL and the oauth2-proxy --redirect-url
- the Keycloak hermes-agent-proxy rootUrl
- operator docs, skills, the ZAP baseline target and the triage monitor default
What stays dual-homed until retirement:
- CoreDNS hosts entry, both agent Ingress rules, certificate SANs
- API_SERVER_CORS_ORIGINS (now a comma-separated pair)
- the Keycloak redirect URIs, web origins and post-logout origins, so a
rollback only needs the oauth2-proxy --redirect-url reverted and does not
require re-running the ensure job
ensure_proxy_client now takes optional trailing legacy URLs; called with a
single URL it emits the identical payload as before, so the chat and triage
clients are unaffected. The ensure Job is bumped to -11 so Flux re-runs it;
login on the new host fails until that Job completes.
Because the session and CSRF cookies use the __Host- prefix they are bound to
one origin, so a fresh login must start on worker.bstein.dev and existing
sessions do not carry over -- re-login is required after rollout.
Knowledge catalogs and diagrams regenerated with `make knowledge`.
2026-08-21 10:00:15 +00:00
|
|
|
192.168.22.9 worker.bstein.dev
|
2026-01-15 16:29:32 -03:00
|
|
|
fallthrough
|
|
|
|
|
}
|
|
|
|
|
}
|
