feat: deploy to Frostmoln production

0 Fork 0

The AWS deploy-prod job has failed since CI left AWS (no k8s.unbound.se
context on the runners). Deploys now go to the Frostmoln production
cluster (namespace schemas), the way the sites do.

Frostmoln enforces restricted Pod Security: the pod runs as the image's
non-root user with a matching securityContext. The prod-only manifests
move to the prod-frostmoln target; the ALB ingress becomes a Traefik one
with a Let's Encrypt certificate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ma8eHhW59hLAJuLzBnLvUu

This commit is contained in:

argoyleandClaude Opus 5.5 committed 2026-10-14 22:15:38 +02:00

1 parent acf6f8df62

commit 1646ee1bc3

8 files changed

+63 -38

No files matched your search

									
										k8s/pdb-prod-frostmoln.yaml
									
		+9
		
												View File
												
				@@ -0,0 +1,9 @@

				apiVersion: policy/v1

				kind: PodDisruptionBudget

				metadata:

				  name: schemas-app

				spec:

				  minAvailable: 1

				  selector:

				    matchLabels:

				      app.kubernetes.io/name: schemas-app