CoreDNS pods in not running state after Guest cluster upgrade to 1.25.

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

Multiple pods, including coreDNS pods not running after the Guest cluster upgrade to 1.25.

Environment

Supervisor 1.27

Guest cluster 1.25

Cause

CoreDNS deployment is in a paused state.

Describing the deployment shows that the status is "progressing" and "DeploymentPaused".

Rollout restart of the deployment gives the following error:

# kubectl rollout restart deployment.apps/coredns -n kube-system
error: deployments.apps "coredns" can't restart paused deployment (run rollout resume first)

Resolution

Unpause the CoreDNS deployment using the following command:

# kubectl patch deployment coredns -n kube-system --type=merge -p '{"spec":{"paused":false}}'