Tennison Yu

> I was having the same issue. But set the annotations values like this and it worked. > > ``` > set { > name = "serviceAccount.annotations.eks\\.amazonaws\\.com/role-arn" > value =...

Hi @dhirschfeld, Sorry about that. Was trying to reproduce an error related to this. Thank you for responding. I'm not sure if this is the right spot to post and...

Hi @dhirschfeld, apologies again, was trying to reproduce part of my troubles above. Any advice would be awesome.

Cool. Thanks @dhirschfeld. The username seems to be pulling now. Not sure why but so happy to get over this hurdle! Though, I seem to have a new problem now......

That's very useful. Thank-you. Will give it a shot. I do have one more sort of side question if you're willing (no worries if not). Part of the process I...

OK, so most of the 500 errors disappeared after I added some more registries. Should've caught that! I am still getting a few 404s though. Are these normal? Example below:...

Thanks @bittrance . That's reassuring. Out of curiosity, do you know about this one too? `expected mirror to respond with 200 OK but received: 500 Internal Server Error` . Did...

Maybe it's normal actually? The msg does say `proxy failed attempting next`. Curious why it's failing though... is it just because the layer is not found? 🤔 Feels like there...

Hmm, I'm not sure. I do see some errors like the below that might actually suggest that error 2 causes error 1 but it's quite noisy so it's a bit...

Wondering if your theory on eventual consistency is correct. It does seem the errors are dying down a bit now.  The way I'm doing the containerd update is through...