Files
aeternalis/deploy/SRS.md
T

2.2 KiB

SRS deployment

Argo CD application: argocd/aeternalis, namespace aeternalis. Endpoint: https://srs.aeternalisgames.com (NGINX HTTPS/443). The chart uses letsencrypt-godaddy, matching SOR, and the srs-tls certificate secret. One initial world is configured at the requested hostname.

Production configuration is deploy/values-srs.yaml. CI publishes a SHA-tagged image to registry.aeternalisgames.com/aeternalis/aeternalis, then promotes its immutable digest into that values file. Values-only promotion commits do not start another build. Argo CD uses the chart and values from this repository. Do not sync the bootstrap image; wait for successful publication and promotion.

External prerequisites (not stored in Git):

  • aeternalis-runtime: DATABASE_URL, OIDC_ISSUER, OIDC_CLIENT_ID, OIDC_CLIENT_SECRET. PostgreSQL uses database aeternalis, dedicated login aeternalis_app, and sslmode=verify-full.
  • postgres-ca ConfigMap: ca.crt, mounted at /etc/postgres-ca/ca.crt. It trusts the database certificate, whose DNS identity is pg-forge-01. A selectorless Service and EndpointSlice resolve that name to the existing PostgreSQL host. Review/update this trust bundle when its certificate rotates.
  • harbor-pull: registry credential for pulling this project's images.
  • Argo CD repository access: a Kubernetes repository Secret, not CI kubeconfig.

OIDC uses the existing aeternalis realm and dedicated confidential client aeternalis-web, authorization-code flow with PKCE S256, and exact callback https://srs.aeternalisgames.com/auth/callback. Existing realm users and policy are preserved. No user passwords or admin credentials are added to the app.

NetworkPolicy permits DNS, PostgreSQL at 172.10.1.127:5432, and the internal NGINX address 172.10.1.160:443 used by the identity provider. Update the explicit allowlists if infrastructure addresses change; do not disable production TLS.

Validate with Helm lint/template for both defaults and SRS values, Kubernetes server-side dry-run, CI tests, registry digest readback, Argo CD Synced/Healthy, HTTPS /readyz, certificate hostname/chain validation, and OIDC redirect checks. A complete interactive login/playtest still requires a real realm user.