Hello DK-8871,
Welcome to microsoft Q&A, Thankyou for posting your query here.
Kubernetes deprecated Docker as a container runtime after version 1.20.It has moved to use container runtime interfaces (CRI) like containerd and CRI-O.
Ensure your cluster and daemonsets are configured to use a supported container runtime like containerd. You might need to update your daemonsets configurations or node setups to accommodate this change.
Check the release notes for the AKS version you upgraded to and any associated node image versions for changes to the container runtime. Adjust your configurations accordingly.
https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions?tabs=azure-cli
Use AKS node pool configurations or daemonsets that are compatible with the AKS-managed environments and their lifecycle management practices, rather than manually configuring nodes.
If the issue persists and you're unable to find a configuration problem, consider reaching out to Azure support. This might be a known issue or require specific guidance based on your cluster's setup.
Hope this helps you.If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!