Ben Poland

> Something that could help a lot would be to have the yaml of a pod that have this issue (a container rewritten but with the corresponding CachedImage not being...

Hi we just had this come up again. I was able to get the DEBUG controller logs: https://gist.github.com/bpoland/604a1ed998e12a4b57e5d3a7dd4b0891 I also grabbed the pod yaml when the issue was happening: https://gist.github.com/bpoland/093f78dad60410597d362dc261ea9861...

> Hi, I've tried to create this pod in my dev cluster. But it successfully created required images. If you try to re-create this pod (with redacted images or not,...

Ah okay, I will try that the next time we see the issue. My guess is that other similar pods using the same new image will not trigger the cachedImage...

Hi, we just hit the issue again. It seems like I can reproduce it pretty consistently by just trying a new image and it does get rewritten on newly-created pods...

Hi, just another data point as this happened again today with another new image. Unfortunately we are using a managed kubernetes setup and don't have access to the api server,...

👋 hi this is happening again today with a new image we're trying to add. Is there anything else we can do to help narrow this down? This is after...

@plaffitt we just had it happen again. I am thinking maybe we will terraform the `Repository` and `CachedImage` resources ourselves manually as a workaround, do you see any issues with...

Ah in the proxy logs on the same node, seems like it's trying but the `Repository` hasn't been created and that breaks it? ``` I0428 18:46:14.221969 1 server.go:158] "proxying request"...

So I created a `Repository` for it manually and that got it past this issue. It still didn't create the `CachedImage` immediately but it wasn't blocking, and it appears that...