2026-07-21 21:02:06 -03:00
|
|
|
# services/hermes/agent-certificate.yaml
|
2026-05-20 17:22:12 -03:00
|
|
|
apiVersion: cert-manager.io/v1
|
|
|
|
|
kind: Certificate
|
|
|
|
|
metadata:
|
2026-08-08 17:59:45 -03:00
|
|
|
name: hermes-sites-tls
|
2026-07-21 21:02:06 -03:00
|
|
|
namespace: hermes
|
2026-05-20 17:22:12 -03:00
|
|
|
spec:
|
2026-08-08 17:59:45 -03:00
|
|
|
secretName: hermes-sites-tls
|
2026-05-20 17:22:12 -03:00
|
|
|
issuerRef:
|
|
|
|
|
kind: ClusterIssuer
|
|
|
|
|
name: letsencrypt
|
|
|
|
|
dnsNames:
|
2026-08-08 17:59:45 -03:00
|
|
|
- agent.hermes.bstein.dev
|
2026-08-21 06:43:18 +00:00
|
|
|
- chat.bstein.dev
|
|
|
|
|
- triage.bstein.dev
|
hermes: restore legacy chat/triage hosts alongside the renamed ones
PR #34 renamed the public chat/triage hosts in place rather than adding
the new names, so chat.hermes.bstein.dev and triage.hermes.bstein.dev
were dropped from the certificate SANs, the hermes-sites Ingress rules
and the CoreDNS overrides at once. Both legacy hosts now answer 404 with
Traefik's default self-signed certificate, and the renamed hosts cannot
complete a login because the Keycloak clients still carry the old
redirect URIs, so chat and triage are unreachable on every hostname.
Make the rename additive, which is the rollback path the post-merge
runbook asks for when the OIDC step fails:
- put the legacy names back on hermes-sites-tls and on the Ingress,
pointing at the same oauth2-proxy backends
- restore both CoreDNS host overrides for in-cluster resolution
- teach ensure_proxy_client to register an optional legacy origin, so
hermes-chat-proxy and hermes-triage-proxy accept the old and new
redirect URIs, web origins and post-logout origins at the same time
while rootUrl stays on the canonical new host
- bump the immutable ensure Job so Flux reruns the script
Serving both names is deliberate: oauth2-proxy cookies are host-bound,
so redirecting the legacy hosts would silently drop live sessions.
Retiring them stays a separate, explicit change.
Supersedes #36, which only bumped the Job and would have left the
legacy hosts dark.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-21 08:49:09 +00:00
|
|
|
# Legacy hosts stay on the certificate until they are retired on purpose;
|
|
|
|
|
# the rename in #34 must not break links or sessions already in flight.
|
|
|
|
|
- chat.hermes.bstein.dev
|
|
|
|
|
- triage.hermes.bstein.dev
|