8 Commits

Include renames

Author	SHA1	Message	Date
argoyle	4da73fb025	feat: deploy to Frostmoln production (#86) ... Moves the production deploy from AWS to the Frostmoln production cluster (namespace `sites`). - `deploy-prod` (AWS) has failed since CI left AWS: the runners have no `k8s.unbound.se` context, so the site on AWS still runs an older image. It's replaced by `deploy-prod-frostmoln`, the same pattern as Shiny's `deploy-frostmoln-staging`: `FROSTMOLN_PRODUCTION_DEPLOY_KEY` + `FROSTMOLN_PRODUCTION_CLUSTER_ID` (org), `BUILDTOOLS_FROSTMOLN_PRODUCTION` (org, target `prod-frostmoln`), `deploy prod-frostmoln -n sites`. - Frostmoln enforces restricted Pod Security: the served image is `nginxinc/nginx-unprivileged` (uid 101, port 8080), with a matching securityContext; the Service is ClusterIP. - `ingress-prod.yaml` (ALB) → `ingress-prod-frostmoln.yaml` (Traefik, Let's Encrypt). Checked locally: the image serves `/health` and `/` (200) as uid 101 with all capabilities dropped. **Merge after** infra's `feat/frostmoln-production-sites` is applied (namespace + org secret). The hostnames keep pointing at AWS until the Route 53 switch, a separate step; the certificate is issued after that. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Ma8eHhW59hLAJuLzBnLvUu Reviewed-on: #86	2026-10-14 17:53:36 +00:00
argoyle	579229732f	chore: ingrass group name	2023-03-03 08:29:28 +01:00
argoyle	339ed1580d	chore: move to default ingress group	2022-12-20 07:14:09 +01:00
argoyle	6d4066a3d4	chore: prepare ingresses for K8S 1.22	2021-09-29 20:02:43 +02:00
argoyle	1ee03e5cf5	chore: add ingress group	2021-04-17 21:56:37 +02:00
argoyle	5441685754	chore: add SSL redirect	2021-04-17 21:52:27 +02:00
argoyle	1aa37fb2f1	chore: move to ALB ingress	2021-04-17 21:39:24 +02:00
argoyle	3c45790cc3	chore: remove ssl redirect since ingress controller handles that	2020-12-05 14:34:31 +01:00