ms2k/remora
SHA256
Watch
0
Code Releases Activity

Harden WebBFF and deployment release behavior

Browse source 
Model fail-closed cross-replica session renewal and implement owner-fenced refresh, transient observer handling, logout fencing, and graceful shutdown. Remove chart-owned Ingress while retaining qualification-owned external routing.
This commit is contained in:
ms2k 2026-07-20 17:09:26 +09:00
commit 414b380516
1 changed files with 980 additions and 136 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/spec/deployment.md
View file

@ -40,7 +40,9 @@ application and NetworkPolicy CIDR allowances.
Containers run non-root with read-only roots, dropped capabilities, resource
limits, and no service links. Worker temporary storage is bounded.
TLS ingress redirects HTTP to HTTPS and emits HSTS. The WebBFF session cookie
The chart exposes ClusterIP Services and does not own north-south routing.
Deployments attach Gateway API `HTTPRoute` resources outside the chart and
enforce HTTPS redirection and HSTS at that boundary. The WebBFF session cookie
is always `Secure`; unencrypted origins are unsupported outside loopback test
environments.