New images in a container registry cant be resolved.

I’ve got a kube cluster connected to a container registry having followed all of the guidance from the docs. I’ve been pushing images for different services for a while and I don’t believe I’ve done anything special outside of that.

Every time I push a new image to the same container registry as of late I get a failure to resolve the image citing :

  Warning  Failed     12m (x4 over 13m)     kubelet            Failed to pull image "registry.digitalocean.com/xxxxxx:xxxxxx": failed to pull and unpack image "registry.digitalocean.com/xxxxxx:xxxxxx": failed to resolve reference "registry.digitalocean.com/xxxxxx:xxxxxx": failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://api.digitalocean.com/v2/registry/auth?scope=repository%3Axxxxx%2Fxxx%2Fxxxx%3Apull&service=registry.digitalocean.com: 401 Unauthorized

It happened once before and last time I disconnected the cluster from the registry via the ui and reconnected it. I don’t think that worked initially but eventually, it started working again. I’m stuck in the same position again and I’m starting to wonder if there’s something about the way in pushing the initial image that could be causing this. when i push updates to existing images everything goes well. it seems to primarily be when I push the first version of an image. I’ve even tried updating the new image after that and pinning versions as I go but to no avail.