Files
ApiCore/deploy/k8s/backend/deployment.yaml
T
Nick Szaunig 41c82d7dc7
Backend Image / build-and-push (push) Successful in 4m44s
Frontend Image / build-and-push (push) Successful in 4m58s
fix: Runner-Label und Registry-Push in Gitea-Actions-Workflows korrigieren
runs-on ubuntu-latest passte auf keinen registrierten Runner (Label
docker-builder erforderlich, siehe funktionierendes Referenzprojekt).
Push laeuft jetzt ueber den cluster-internen Service gitea:80 statt
git.encry.de, da der Cloudflare-Proxy Registry-Blob-Uploads mit "413
Payload Too Large" ablehnt. Auth ueber gitea.actor + REGISTRY_TOKEN
(GITEA_TOKEN hat kein Package-Write-Recht). Image-Pfad wird jetzt
kleingeschrieben (OCI verbietet Grossbuchstaben) - betrifft auch den
Owner-Namen in den K8s-Deployment-Manifesten.
2026-08-26 16:58:28 +02:00

46 lines
1.1 KiB
YAML

apiVersion: apps/v1
kind: Deployment
metadata:
name: apicore-backend
labels:
app: apicore-backend
spec:
replicas: 2
selector:
matchLabels:
app: apicore-backend
template:
metadata:
labels:
app: apicore-backend
spec:
containers:
- name: apicore-backend
image: git.encry.de/nick.rosenloecher/apicore-backend:latest
ports:
- containerPort: 3001
envFrom:
- configMapRef:
name: apicore-backend-config
- secretRef:
name: apicore-backend-secret
livenessProbe:
httpGet:
path: /health
port: 3001
initialDelaySeconds: 10
periodSeconds: 15
readinessProbe:
httpGet:
path: /health/ready
port: 3001
initialDelaySeconds: 5
periodSeconds: 10
resources:
requests:
cpu: 100m
memory: 128Mi
limits:
cpu: 500m
memory: 512Mi