Registry authentication errors happen when Kubly cannot push to or pull from the configured Harbor-compatible registry.
- Covers
401 or 403 registry responses.
- Covers push failures during Git builds.
- Covers deploy-time image pull failures caused by stale or invalid pull credentials.
- A repo build cannot push an image.
- A deployment cannot pull a private image.
- Registry repository or project creation fails.
- Registry integration enabled.
- Valid registry credentials.
- Permission to create or use the target repository.
Screenshot Required
- Check whether the error happens during image push or image pull.
- Confirm the registry host in the image reference is correct.
- Confirm the repository or project exists.
- Confirm the credentials have permission for the action.
- Rotate or recreate credentials if they are stale.
- Retry the build or redeploy the app.
- Fixing push credentials while the problem is actually a workload pull secret.
- Using the wrong registry host.
- Deleting a repository that still backs a deployment.
- Separate build-time registry access from deploy-time pull access when troubleshooting.
- Use explicit image tags so you can confirm exactly which artifact should be pulled.