Recovered autocoder-engine and codecartography-frontend rollouts after Kubernetes failed to pull private Gitea registry images.
codecartography-frontend pod entered ImagePullBackOff for image:
gitea.app.lan/autocoder/autocoder-engine-frontend:sha-3f9941814774
Kubelet event reported:
pull access denied, repository does not exist or may require authorization: authorization failed: no basic auth credentials
Namespace autocoder-engine had the required Docker registry Secret gitea-registry-cred, but the autocoder-engine and codecartography-frontend Deployment pod templates did not reference it via imagePullSecrets.
Patched live Deployments in namespace autocoder-engine to include:
imagePullSecrets:
- name: gitea-registry-cred
Updated repository-managed manifest:
/home/ax_julian/AutoCoder-Engine/k8s/05-deployment-service-ingress.yaml
kubectl kustomize --load-restrictor=LoadRestrictionsNone /home/ax_julian/AutoCoder-Engine/k8s completed successfully.Deployment/codecartography-frontend rolled out successfully.Deployment/autocoder-engine rolled out successfully.1/1 ready and reference gitea-registry-cred.This was exposed by a new immutable image rollout from Gitea Actions. The issue was independent of the second runner itself; runner 2 successfully built/scheduled the workflow, but the cluster runtime lacked pull credentials in the pod templates.