Customer Portal — placeholder
This is not the application. It is a static page proving the serving path exists, so that the real bundle is one image reference away.
What this page proves
- DNS resolves portal.tdcp.dis.thales.team to the cluster load balancer.
- TLS terminates on a certificate issued by Let's Encrypt over HTTP-01.
- The pod runs non-root under restricted PodSecurity and serves on 8080.
- The response carries the portal's Content-Security-Policy and its security headers.
- Tenant facts are mounted, not built in — see /config.json.
- The application bundle is not here yet.
Silo
- Tenant
- dev-1
- Portal origin
- https://portal.tdcp.dis.thales.team
- API origin
- https://api.tdcp.dis.thales.team
- Runtime config
- /config.json
- Health
- /healthz
Replacing this page
The image reference is set in deployment/apps/portal/clusters/dev-1/kustomization.yaml. Point it at the portal's own build, drop the placeholder patch, and the pipeline's pin:dev job takes over the digest from then on.