Hi @benjoldersma ,
thanks for all the information.
Regarding the issue with the images to be pulled. The error you are getting is because the cache system mentioned by Ramiro. When an image is built and the working directory is clean, images are pushed to <registry-url>/okteto/<image-name> (the shortcut is okteto.global/<image>) instead of <registry-url>/<namespace>/<image-name> (the shortcut is okteto.dev/<image>). The reason because of that is because the image pushed to okteto.global is accessible by all the users, so they don’t have to build it again.
So the issues seems to be that image is being pushed to okteto.global but then, the manifest is pulling from okteto.dev and that doesn’t exist. You can check it checking the image pushed. The recommended way to achieve what you want is to do something similar to what we have in our movies example. You should use the environment variables we generate OKTETO_BUILD_<service-name>_XXXX and pass it to helm. So it will pass the right image built during the process.
On the other hand, related to BuildKit issue. I wanted to know if, BuildKit stopped working because maybe in the upgrade to 1.10 you also changed the BuildKit values and as the route 53 entry was missing, that was expected. Or, on the contrary, BuildKit stopped working after the upgrade and the, you changed the config values to try to fix it. Anyways, we will try to reproduce the issue to see if during the upgrade something breaks BuildKit. Thank you so much for the information.
Let us know if you have any other question or the proposed solution doesn’t work for the image issue.