got 403 Forbidden when pulling new image after upgrading from 1.3.0 to 1.8.0
rucciva opened this issue · comments
hello, after upgrading from 1.3.0 to 1.8.0, we noticed error 403 when pulling cached image.
registry and proxy does not show any log, what could be the reason?
thanks
Failed to pull image "localhost:7439/redis:7.0.9-alpine3.17": rpc error: code = Unknown desc = failed to pull and unpack image "localhost:7439/redis:7.0.9-alpine3.17": failed to resolve reference "localhost:7439/redis:7.0.9-alpine3.17": pulling from host localhost:7439 failed with status code [manifests 7.0.9-alpine3.17]: 403 Forbidden
Hello,
Most probably it is because the cache has been wiped-out. The upgrade from 1.6.0 to 1.7.0 includes a change in the way CRDs are installed and if you installed CRDs through the chart (using the installCRD value), upgrading to 1.7.0 required to recreate CRDs.
I hope that wasn't too inconvenient for you.
i did recreate the CRD though, i was using argocd with kustomize that generate manifest from the helm package. do i need to manually delete the cache first?
Not that the existing cache doesn't seems to be deleted since when i revert back to 1.3.0, it was working without redownloading
i end up uninstalling the old kuik, delete cachedImage, delete the cache stored in s3 bucket, and install the new version of kuik.
Thanks