bcs-website/k8s/deployment.yaml
Brad Rodgers b9f2c72bd4
All checks were successful
CI / ci (push) Successful in 1m55s
deploy: private package pull via External Secrets; pull over public HTTPS (no k3s restart)
- k3s pulls git.7tl-homelab.com/... over valid TLS (no registries.yaml/node config)
- CI still pushes internally to 10.66.15.22:3000 (fast, insecure-trusted)
- ExternalSecret materializes gitea-registry dockerconfigjson from OpenBao
- deployment uses imagePullSecrets: gitea-registry
- .env added to .dockerignore
2026-07-17 07:36:22 -04:00

48 lines
1.3 KiB
YAML

apiVersion: apps/v1
kind: Deployment
metadata:
name: bluecap-website
namespace: bluecap-strategies
spec:
replicas: 2
selector:
matchLabels:
app: bluecap-website
template:
metadata:
labels:
app: bluecap-website
spec:
# Private Gitea package -> pull auth from the External-Secrets-managed dockerconfigjson
# (see k8s/externalsecret-registry.yaml).
imagePullSecrets:
- name: gitea-registry
containers:
- name: website
# Pulled over public HTTPS (valid cert -> no node registry config). Tag managed by CI
# via kustomize (see k8s/kustomization.yaml `images`).
image: git.7tl-homelab.com/bmr_bluecap/bcs-website:latest
imagePullPolicy: IfNotPresent
ports:
- name: http
containerPort: 80
readinessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 5
periodSeconds: 10
livenessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 15
periodSeconds: 20
resources:
requests:
cpu: 25m
memory: 64Mi
limits:
cpu: 250m
memory: 128Mi