Kubelet Skipping POD Sync Activities

[strikingraghu]

/kube-dns

What happened:
I have deployed kube-dns yaml file for a 3 master / 3 node cluster and it's failing to run KUBE-DNS pods within this cluster. I have restarted all the processes, verified network and settings as well. All seems to be OK within the ecosystem, but it fails to run these DNS pods and throws "Skipping Pod Sync Activities - Container runtime is down"

What you expected to happen:
We need to run these basic KUBE-DNS pods within the cluster to provide DNS capabilities

How to reproduce it (as minimally and precisely as possible):
You can refer to this YAML file for Kube-DNS deployments

Anything else we need to know?:
N/A

Environment:

• Kubernetes version (use kubectl version): v1.15
• Cloud provider or hardware configuration: VMware VM / CentOS 7
• OS (e.g: cat /etc/os-release): CentOS 7
• Kernel (e.g. uname -a): Linux kube-controller-01 3.10.0-1062.4.3.el7.x86_64 Unit test coverage in Kubelet is lousy. (~30%) #1 SMP Wed Nov 13 23:58:53 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
• Install tools:
• Network plugin and version (if this is a network-related bug): N/A
• Others:

[strikingraghu]

/sig dns
/sig kube-dns

[k8s-ci-robot]

@strikingraghu: The label(s) sig/dns, sig/kube-dns cannot be applied, because the repository doesn't have them

In response to this:

/sig dns
/sig kube-dns

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[strikingraghu]

/sig coredns
/sig containerd
/sig kube-dns
/sig kubelet

[k8s-ci-robot]

@strikingraghu: The label(s) sig/coredns, sig/containerd, sig/kube-dns, sig/kubelet cannot be applied, because the repository doesn't have them

In response to this:

/sig coredns
/sig containerd
/sig kube-dns
/sig kubelet

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[strikingraghu]

/sig Scheduling
/sig Multicluster

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.