Running kubelet --pod-manifest-path=/newdir returns errors.
It's not clear to me where I can add the --pod-manifest-path to a systemd file on Ubuntu. I know for v1.12 there is the KubeletConfiguration type but I am using v1.11.
Asked
Active
Viewed 1,221 times
0
Ishara Madhawa
- 3,549
- 5
- 24
- 42
R678
- 85
- 9
-
How did you provision your cluster? – nightfury1204 Dec 02 '18 at 06:37
-
I'm practicing troubleshooting. Where exactly should I look to apply the pod-manifest-path? In the docs they have an example only for Fedora that isn't helpful – R678 Dec 02 '18 at 07:10
1 Answers
1
You can find in documentation:
Configure your kubelet daemon on the node to use this directory by running it with
--pod-manifest-path=/etc/kubelet.d/argument. On Fedora edit/etc/kubernetes/kubeletto include this line:KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --pod-manifest-path=/etc/kubelet.d/"Instructions for other distributions or Kubernetes installations may vary.
Restart kubelet. On Fedora, this is:
[root@my-node1 ~] $ systemctl restart kubelet
If you want to use --pod-manifest-path you can define it in Kubelet configuration.
Usually it is stored /etc/kubernetes/kubelet or /etc/default/kubelet or /etc/systemd/system/kubelet.service
Nick Rak
- 2,629
- 13
- 19
-
Any ideas where in the kubelet configuration it can be defined? Here https://kubernetes.io/docs/reference/config-api/kubelet-config.v1beta1/ it simply doesn't exist. Other directives which have been deprecated as command line arguments (like cgroupdrivers) do exist. – Lethargos Jun 01 '23 at 00:24