Kind: make necessary `/etc/kubernetes/manifests` in workers to avoid unnecessary error logs

[brightzheng100]

What happened:

In workers, as the folder of /etc/kubernetes/manifests doesn't exist by default to cater for static pods, kubelet will keep throwing errors complaining path does not exist, ignoring.

# journalctl -f
...
Oct 23 07:35:58 kind-cluster-worker kubelet[508]: E1023 07:35:58.547619     508 file_linux.go:61] Unable to read config path "/etc/kubernetes/manifests": path does not exist, ignoring
...

What you expected to happen:

The folder should be created by default to avoid such annoying warnings prompting up in journalctl logs.

How to reproduce it (as minimally and precisely as possible):

Spin up a kind cluster and run:

$ docker exec --privileged -i kind-cluster-worker journalctl -f

Anything else we need to know?:

Simply create that folder can stop such warnings:

docker exec --privileged -i kind-cluster-worker mkdir -p /etc/kubernetes/manifests

Environment:

• kind version: (use kind version): v0.5.1
• Kubernetes version: (use kubectl version):
• Docker version: (use docker info):
• OS (e.g. from /etc/os-release): MacBook Pro

[BenTheElder]

IMO kubeadm is nominally responsible for this but I'd be Ok with creating it to avoid log spam

Cc @neolit123

[aojea]

/label help-wanted
/label good-first-issue

[k8s-ci-robot]

@aojea: The label(s) /label help-wanted , /label good-first-issue cannot be applied. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other

In response to this:

/label help-wanted
/label good-first-issue

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.

[BenTheElder]

/remove-kind bug
/kind feature
(If this is a bug, I say it's a kubeadm bug, adding the directory to kind to prevent non breaking log noise is a feature imo 🙃, we try pretty hard to avoid allowing actual bugs to occur)

[k8s-ci-robot]

@BenTheElder: Those labels are not set on the issue: kind/bug

In response to this:

/remove-kind bug
/kind feature
(If this is a bug, I say it's a kubeadm bug)

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.

[k8s-ci-robot]

@BenTheElder: Those labels are not set on the issue: kind/bug

In response to this:

/remove-kind bug
/kind feature
(If this is a bug, I say it's a kubeadm bug, adding the directory to kind to prevent non breaking log noise is a feature imo 🙃, we try pretty hard to avoid allowing actual bugs to occur)

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.

[BenTheElder]

Re-upgrading to a bug. Kubeadm expects to be installed by Deb or RPM, apparently it is ensured there.

mkdir -p /etc/kubernetes/manifests is in the post-install for kubelet.

/remove-kind feature
/kind bug
/assign

[BenTheElder]

https://github.com/kubernetes-sigs/kind/pull/1003 will fix this

[neolit123]

mkdir -p /etc/kubernetes/manifests is in the post-install for kubelet.

yes, joining nodes don't need the path but the package just ensures it's there.
joining workers still have the option to create static pods.