Why I can't find kube-proxy.yaml file in /etc/kubernetes/manifests? isn't deploy . . .

Ceci Ivanov:
why I can’t find kube-proxy.yaml file in /etc/kubernetes/manifests?
isn’t deployed as a pod like the other ones (etcd kube-apiserver …) ?

Radoslaw Czajkowski:
kube-proxy is a deamonset

Radoslaw Czajkowski:
you can edit the deamonset

Radoslaw Czajkowski:
i was also looking for this deamonset yaml file but found none

Radoslaw Czajkowski:
i guess it comes with a kubeadm install internally, or maybe someone knows where the code for the deamonset is stored?

Marko Eremija:
Shouldn’t kube proxy be installed on worker nodes? Are you looking for it on the right node?

Radoslaw Czajkowski:
it will be installed on all nodes of the cluster (including control nodes). It is a deamonset - one pod per node

Alistair Mackay:

kubectl get daemonset kube-proxy -n kube-system -o yaml

Radoslaw Czajkowski:
@Alistair Mackay but it’s interesting that this daemonset yaml definition must exist somewhere on a disk for the kube-proxy to be even created. If the ds is running then it got the declarative yaml definition from somewhere to start it up. So where is it stored?

Alistair Mackay:
If it’s a kubeadm cluster, the manifest will be either contained within, or downloaded when kubeadm init is run
You would need to put a trace on your network interface when it is running to see exactly what gets downloaded from where