Repository for tools and artifacts related to the sig-windows charter in Kubernetes. Scripts to assist kubeadm and wincat and flannel will be hosted here.
Apache License 2.0
123
stars
123
forks
source link
kubelet log spam when path "c:/etc/kubernetes/manifests" doesn't exist #334
Describe the bug
After installing containerd and kubelet via the Install-Containerd.ps1 and PrepareNode.ps1 scripts, I found the following log spam in the kubelet.err.log:
E0627 18:06:30.995288 584 file.go:104] "Unable to read config path" err="path does not exist, ignoring" path="C:\\etc\\kubernetes\\manifests"
I proceeded to install Calico and everything works fine in the cluster. The only issue is the message repeats periodically, filling up the logs. I believe since the error message says "ignoring", nothing severe is affected, but I checked and the path does in fact not exist. Creating it with mkdir -Force c:/etc/kubernetes/manifests fixes it.
To Reproduce
Steps to reproduce the behavior:
Install kubelet via the PrepareNode.ps1 script. Install CNI (not sure if this would only happen with Calico, but only tested on it). Check kubelet logs.
Expected behavior
Kubernetes (please complete the following information):
Describe the bug After installing containerd and kubelet via the Install-Containerd.ps1 and PrepareNode.ps1 scripts, I found the following log spam in the kubelet.err.log:
I proceeded to install Calico and everything works fine in the cluster. The only issue is the message repeats periodically, filling up the logs. I believe since the error message says "ignoring", nothing severe is affected, but I checked and the path does in fact not exist. Creating it with
mkdir -Force c:/etc/kubernetes/manifestsfixes it.To Reproduce Steps to reproduce the behavior: Install kubelet via the PrepareNode.ps1 script. Install CNI (not sure if this would only happen with Calico, but only tested on it). Check kubelet logs.
Expected behavior
Kubernetes (please complete the following information):
Additional context N/A