kubernetes 1.12.2 failed to load Kubelet config file /var/lib/kubelet/config.yaml

Environment:

Kubernetes 1.12.2

Docker 18.9.0

microk8s.kubectl

$ k get all

NAME                                          READY   STATUS             

RESTARTS   AGE

pod/mysql-0                                   1/1     Running            0          72s

pod/nginx-ingress-microk8s-controller-c2pgz   0/1     CrashLoopBackOff   129        22h

pod/web-0                                     1/1     Running            0          78s



NAME                    TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE

service/kubernetes      ClusterIP   10.152.183.1   <none>        443/TCP    70m

service/mysql-service   ClusterIP   None           <none>        3306/TCP   72s

service/nginx-service   ClusterIP   None           <none>        80/TCP     78s



NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE

daemonset.apps/nginx-ingress-microk8s-controller   1         1         0       1            0           <none>          2d22h



NAME                     DESIRED   CURRENT   AGE

statefulset.apps/mysql   1         1         72s

statefulset.apps/web     1         1         78s

/var/log/syslog:

failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory



Error syncing pod f0ab0f74-e6f2-11e8-8410-482ae31e6a94 ("nginx-ingress-microk8s-controller-c2pgz_default(f0ab0f74-e6f2-11e8-8410-482ae31e6a94)"), skipping: failed to "StartContainer" for "nginx-ingress-microk8s" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=nginx-ingress-microk8s pod=nginx-ingress-microk8s-controller-c2pgz_default(f0ab0f74-e6f2-11e8-8410-482ae31e6a94)"

What is nginx-ingress-microk8s-controller-c2pgz? Who started it?

edited Nov 14 '18 at 2:23

asked Nov 13 '18 at 8:37

Kok How Teh

87314

Is it happening while joining the worker node? Or the system was already running and it started happening? Is /var/lib/kubelet/config.yaml present on the system?

– Prafull Ladha
Nov 13 '18 at 9:03

No. The file is missing.

– Kok How Teh
Nov 13 '18 at 13:16

what do you mean by "No"? Can you share information what you are trying to do, your cluster architecture and when exactly you faces with this error?

– VKR
Nov 13 '18 at 15:24

I think it is due to the fact that kubeadm init fails: github.com/kubernetes/kubeadm/issues/1239

– Kok How Teh
Nov 14 '18 at 6:02

add a comment |

Environment:

Kubernetes 1.12.2

Docker 18.9.0

microk8s.kubectl

$ k get all

NAME                                          READY   STATUS             

RESTARTS   AGE

pod/mysql-0                                   1/1     Running            0          72s

pod/nginx-ingress-microk8s-controller-c2pgz   0/1     CrashLoopBackOff   129        22h

pod/web-0                                     1/1     Running            0          78s



NAME                    TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE

service/kubernetes      ClusterIP   10.152.183.1   <none>        443/TCP    70m

service/mysql-service   ClusterIP   None           <none>        3306/TCP   72s

service/nginx-service   ClusterIP   None           <none>        80/TCP     78s



NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE

daemonset.apps/nginx-ingress-microk8s-controller   1         1         0       1            0           <none>          2d22h



NAME                     DESIRED   CURRENT   AGE

statefulset.apps/mysql   1         1         72s

statefulset.apps/web     1         1         78s

/var/log/syslog:

failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory



Error syncing pod f0ab0f74-e6f2-11e8-8410-482ae31e6a94 ("nginx-ingress-microk8s-controller-c2pgz_default(f0ab0f74-e6f2-11e8-8410-482ae31e6a94)"), skipping: failed to "StartContainer" for "nginx-ingress-microk8s" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=nginx-ingress-microk8s pod=nginx-ingress-microk8s-controller-c2pgz_default(f0ab0f74-e6f2-11e8-8410-482ae31e6a94)"

What is nginx-ingress-microk8s-controller-c2pgz? Who started it?

edited Nov 14 '18 at 2:23

asked Nov 13 '18 at 8:37

Kok How Teh

87314

Is it happening while joining the worker node? Or the system was already running and it started happening? Is /var/lib/kubelet/config.yaml present on the system?

– Prafull Ladha
Nov 13 '18 at 9:03

No. The file is missing.

– Kok How Teh
Nov 13 '18 at 13:16

what do you mean by "No"? Can you share information what you are trying to do, your cluster architecture and when exactly you faces with this error?

– VKR
Nov 13 '18 at 15:24

I think it is due to the fact that kubeadm init fails: github.com/kubernetes/kubeadm/issues/1239

– Kok How Teh
Nov 14 '18 at 6:02

add a comment |

Environment:

Kubernetes 1.12.2

Docker 18.9.0

microk8s.kubectl

$ k get all

NAME                                          READY   STATUS             

RESTARTS   AGE

pod/mysql-0                                   1/1     Running            0          72s

pod/nginx-ingress-microk8s-controller-c2pgz   0/1     CrashLoopBackOff   129        22h

pod/web-0                                     1/1     Running            0          78s



NAME                    TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE

service/kubernetes      ClusterIP   10.152.183.1   <none>        443/TCP    70m

service/mysql-service   ClusterIP   None           <none>        3306/TCP   72s

service/nginx-service   ClusterIP   None           <none>        80/TCP     78s



NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE

daemonset.apps/nginx-ingress-microk8s-controller   1         1         0       1            0           <none>          2d22h



NAME                     DESIRED   CURRENT   AGE

statefulset.apps/mysql   1         1         72s

statefulset.apps/web     1         1         78s

/var/log/syslog:

failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory



Error syncing pod f0ab0f74-e6f2-11e8-8410-482ae31e6a94 ("nginx-ingress-microk8s-controller-c2pgz_default(f0ab0f74-e6f2-11e8-8410-482ae31e6a94)"), skipping: failed to "StartContainer" for "nginx-ingress-microk8s" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=nginx-ingress-microk8s pod=nginx-ingress-microk8s-controller-c2pgz_default(f0ab0f74-e6f2-11e8-8410-482ae31e6a94)"

What is nginx-ingress-microk8s-controller-c2pgz? Who started it?

edited Nov 14 '18 at 2:23

asked Nov 13 '18 at 8:37

Kok How Teh

87314

Environment:

Kubernetes 1.12.2

Docker 18.9.0

microk8s.kubectl

$ k get all

NAME                                          READY   STATUS             

RESTARTS   AGE

pod/mysql-0                                   1/1     Running            0          72s

pod/nginx-ingress-microk8s-controller-c2pgz   0/1     CrashLoopBackOff   129        22h

pod/web-0                                     1/1     Running            0          78s



NAME                    TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE

service/kubernetes      ClusterIP   10.152.183.1   <none>        443/TCP    70m

service/mysql-service   ClusterIP   None           <none>        3306/TCP   72s

service/nginx-service   ClusterIP   None           <none>        80/TCP     78s



NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE

daemonset.apps/nginx-ingress-microk8s-controller   1         1         0       1            0           <none>          2d22h



NAME                     DESIRED   CURRENT   AGE

statefulset.apps/mysql   1         1         72s

statefulset.apps/web     1         1         78s

/var/log/syslog:

failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory



Error syncing pod f0ab0f74-e6f2-11e8-8410-482ae31e6a94 ("nginx-ingress-microk8s-controller-c2pgz_default(f0ab0f74-e6f2-11e8-8410-482ae31e6a94)"), skipping: failed to "StartContainer" for "nginx-ingress-microk8s" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=nginx-ingress-microk8s pod=nginx-ingress-microk8s-controller-c2pgz_default(f0ab0f74-e6f2-11e8-8410-482ae31e6a94)"

What is nginx-ingress-microk8s-controller-c2pgz? Who started it?

docker kubernetes kubelet

edited Nov 14 '18 at 2:23

asked Nov 13 '18 at 8:37

Kok How Teh

87314

edited Nov 14 '18 at 2:23

asked Nov 13 '18 at 8:37

Kok How Teh

87314

edited Nov 14 '18 at 2:23

asked Nov 13 '18 at 8:37

Kok How Teh

87314

asked Nov 13 '18 at 8:37

Kok How Teh

87314

asked Nov 13 '18 at 8:37

Kok How Teh

87314

Is it happening while joining the worker node? Or the system was already running and it started happening? Is /var/lib/kubelet/config.yaml present on the system?

– Prafull Ladha
Nov 13 '18 at 9:03

No. The file is missing.

– Kok How Teh
Nov 13 '18 at 13:16

what do you mean by "No"? Can you share information what you are trying to do, your cluster architecture and when exactly you faces with this error?

– VKR
Nov 13 '18 at 15:24

I think it is due to the fact that kubeadm init fails: github.com/kubernetes/kubeadm/issues/1239

– Kok How Teh
Nov 14 '18 at 6:02

add a comment |

Is it happening while joining the worker node? Or the system was already running and it started happening? Is /var/lib/kubelet/config.yaml present on the system?

– Prafull Ladha
Nov 13 '18 at 9:03

No. The file is missing.

– Kok How Teh
Nov 13 '18 at 13:16

what do you mean by "No"? Can you share information what you are trying to do, your cluster architecture and when exactly you faces with this error?

– VKR
Nov 13 '18 at 15:24

I think it is due to the fact that kubeadm init fails: github.com/kubernetes/kubeadm/issues/1239

– Kok How Teh
Nov 14 '18 at 6:02

Is it happening while joining the worker node? Or the system was already running and it started happening? Is /var/lib/kubelet/config.yaml present on the system?

– Prafull Ladha
Nov 13 '18 at 9:03

No. The file is missing.

– Kok How Teh
Nov 13 '18 at 13:16

what do you mean by "No"? Can you share information what you are trying to do, your cluster architecture and when exactly you faces with this error?

– VKR
Nov 13 '18 at 15:24

I think it is due to the fact that kubeadm init fails: github.com/kubernetes/kubeadm/issues/1239

– Kok How Teh
Nov 14 '18 at 6:02

add a comment |

0

active

oldest

votes

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53276901%2fkubernetes-1-12-2-failed-to-load-kubelet-config-file-var-lib-kubelet-config-yam%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

0

active

oldest

votes

0

active

oldest

votes

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Wsrtjtyk