Comment 1 for bug 1891530

Task to Chris on MM and gathered some info.

In this case, the customer cluster had just upgraded to 1.17.10:

kubernetes-master 1.17.10 active 3 kubernetes-master local 0 ubuntu
kubernetes-worker 1.17.10 active 3 kubernetes-worker local 0 ubuntu exposed

The customer (who is using their own registry) now has pods in ImagePullBackoff because their registry doesn't have nvidia/k8s-device-plugin:v0.7.0-rc.5

Looking at https://github.com/charmed-kubernetes/bundle/blob/master/container-images.txt at the time of this writing, we can see that the latest version of cdk-addons is 1.17.9, and that this image did indeed change since 1.17.8 (and in fact, it has changed 6 times in the 1.17.x series).