Stéphane Tailland fd2df93683 fix(deploy): the ghcr package is private, so declare the pull secret ...

Same arrangement classic-models already uses: a hand-created ghcr-pull-secret
rather than one committed or held in Vault, since the credential is a GitHub
token that belongs to no estate in particular. Without it the pod would sit in
ImagePullBackOff with no hint as to why.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-29 07:16:40 +02:00

..

ca-configmap.yaml

feat: deploy the agent — image, manifests, and the Flux plumbing

2026-08-28 17:50:02 +02:00

configmap.yaml

feat: deploy the agent — image, manifests, and the Flux plumbing

2026-08-28 17:50:02 +02:00

deployment.yaml

fix(deploy): the ghcr package is private, so declare the pull secret

2026-08-29 07:16:40 +02:00

externalsecret.yaml

feat: deploy the agent — image, manifests, and the Flux plumbing

2026-08-28 17:50:02 +02:00

kustomization.yaml

feat: deploy the agent — image, manifests, and the Flux plumbing

2026-08-28 17:50:02 +02:00

namespace.yaml

feat: deploy the agent — image, manifests, and the Flux plumbing

2026-08-28 17:50:02 +02:00

service.yaml

feat: deploy the agent — image, manifests, and the Flux plumbing

2026-08-28 17:50:02 +02:00