Connection refused when using k8s.gcr.io/coredns:1.6.7 image

[Tessg22]

Section 3. Advanced Scheduling:

• coredns pods in CrashLoopBackOff status when trying to recreate
• Inspect of docker container: "Error": "OCI runtime create failed: container_linux.go:367: starting container process caused: exec: \"/coredns\": stat /coredns: no such file or directory: unknown"
• Deployment logs: E0502 18:35:32.526725 1 reflector.go:307] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:105: Failed to watch *v1.Namespace: Get https://10.96.0.1:443/api/v1/namespaces?allowWatchBookmarks=true&resourceVersion=864&timeout=7m42s&timeoutSeconds=462&watch=true: dial tcp 10.96.0.1:443: connect: connection refused E0502 18:35:32.526855 1 reflector.go:307] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:105: Failed to watch *v1.Endpoints: Get https://10.96.0.1:443/api/v1/endpoints?allowWatchBookmarks=true&resourceVersion=13213&timeout=5m51s&timeoutSeconds=351&watch=true: dial tcp 10.96.0.1:443: connect: connection refused E0502 18:35:32.526902 1 reflector.go:307] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:105: Failed to watch *v1.Service: Get https://10.96.0.1:443/api/v1/services?allowWatchBookmarks=true&resourceVersion=874&timeout=6m30s&timeoutSeconds=390&watch=true: dial tcp 10.96.0.1:443: connect: connection refused

I have upgraded packages and as workaround changed image in coredns deployment to the latest docker.io/coredns/coredns:1.8.3 which made pods to be in Ready state again