feat(local): pull sunbeam-proxy from Gitea registry; switch to imagePullPolicy Always

Image is now built and pushed by `sunbeam.py --build` rather than imported
directly into k3s containerd. imagePullPolicy changes from Never to Always
so every rollout restart pulls the freshly pushed image.
This commit is contained in:
2026-03-02 18:54:56 +00:00
parent e0f1803e33
commit cc2d4e6cbd
2 changed files with 5 additions and 6 deletions

View File

@@ -22,12 +22,11 @@ resources:
- ../../base/vso - ../../base/vso
images: images:
# Local dev: sunbeam-proxy is built and imported directly into k3s containerd. # Pulled from our Gitea registry. Built and pushed by: sunbeam.py --build
# imagePullPolicy: Never is set in values-pingora.yaml so k3s never tries to pull. # imagePullPolicy: Always in values-pingora.yaml ensures each rollout pulls fresh.
# Production overlay points this at src.DOMAIN_SUFFIX/studio/sunbeam-proxy:latest.
- name: sunbeam-proxy - name: sunbeam-proxy
newName: sunbeam-proxy newName: src.DOMAIN_SUFFIX/studio/sunbeam-proxy
newTag: dev newTag: latest
# amd64-only La Suite images — mirrored to our Gitea registry with a patched # amd64-only La Suite images — mirrored to our Gitea registry with a patched
# OCI index that adds an arm64 alias so Rosetta can run them on the Lima VM. # OCI index that adds an arm64 alias so Rosetta can run them on the Lima VM.

View File

@@ -12,7 +12,7 @@ spec:
spec: spec:
containers: containers:
- name: pingora - name: pingora
imagePullPolicy: Never imagePullPolicy: Always
ports: ports:
# Bind HTTP/HTTPS directly to the Lima VM's host network # Bind HTTP/HTTPS directly to the Lima VM's host network
- name: http - name: http