This message was deleted.

PS: i dont see this issue when upgrading to 1.32. kube-system pods are only restarted after master has loaded the images in agent/images folder in the local registry

The kubelet doesn't even get started until after all the images are imported, regardless of version. What do the service logs show during startup?

Thanks @creamy-pencil-82913 for the response.

Oh, I see, you're saying that the server upgrade caused new pods to run on the agents, but the agents hadn't been upgraded yet so they hadn't imported the images

yes thats the exact behavior thats happening

Are you using spegel?

yes Im using embedded registry.

You might consider preloading the images before the upgrade

You mean to move the tar.zst to images folder and restart k3s server before an upgrade? I had only moved tar.zst to images folder in the prepare step. Im expecting cluster upgrade to handle the k3s restart. tho I see the correct behavior in 1.32, What really changed in 1.32? kube-system pods get scheduled/restarted on agents only after the images are completed loaded in the registry.