Check rendered kustomize output in the deploy policy (M9.8f review)
The policy check now renders every overlay with pinned, checksum-verified kustomize v5.8.1 (ADR-0088) and validates effective namespaces, session/input/ listener environment and arguments, ports, Services, quotas, policies, Ingresses and Secrets, so inline/JSON patches and namespace changes cannot bypass it. Route enabling is gated on an ADR-0087 amendment with tested server windows, route addresses must be RFC 1918 or explicitly approved, and the Local health-check node port is documented with its enabling evidence. Self-test grows to 33 cases. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -89,5 +89,6 @@ ADR-0087 designs `void.aeternalisgames.com:7400` through a dedicated internal Me
|
||||
VIP to the region pod (TLS end to end, development/test CIDR only), opened only in
|
||||
operator windows that evo-server itself expires. The manifests are in
|
||||
`deploy/kubernetes/region/dev-session-route` and are not included anywhere; the policy
|
||||
check refuses to enable them until the VIP, client CIDR, dev quota and the server-side
|
||||
`--session-window` exist. Until then use the port-forward procedures above.
|
||||
check refuses to enable them until the VIP, client CIDR, dev quota and server-enforced
|
||||
session windows exist (ADR-0087 enabling list). Until then use the port-forward
|
||||
procedures above.
|
||||
|
||||
Reference in New Issue
Block a user