<p>I'm new to Kubernetes development, and I have a task to change some features in Kuberenetes services. </p>

<p>I have the <a href="https://github.com/kubernetes/community/tree/master/contributors/devel#readme" rel="nofollow noreferrer">Kubernetes local cluster</a>, and also I have a testbed consisting of 4 RPI's, My first changes were done over <code>Kubectl</code>, and what I have done was cross compiling the binaries on my machine and then replacing the old binaries found in the RPI's (since compiling the code in  the RPI's is time-consuming). </p>

<p>Now, I have reached a point where I have to update some changes to <code>Kube-proxy</code>, in the local cluster the binary files are in <code>_output/bin</code>, however in the real cluster the Kube-proxy is running in a container (for each node), so changing the binaries would need creating new Docker images and forcing Kubernetes to choose those images instead of the default ones (as far as I understood). </p>

<p>So My questions: </p>

<ol>
<li><p>What is the best/easiest way to push the changes on <code>Kube-proxy</code> on the running cluster? </p></li>
<li><p>If I compiled the code in the RPI, the <code>make</code> will release a binary file of <code>Kube-proxy</code>, but how the cluster will take those changes?</p></li>
</ol>

<p>Cluster Spec's: </p>

<ol>
<li><p>Kubernetes v1.9.</p></li>
<li><p>OS hypriotos-v7+.</p></li>
<li><p>Architecture arm 32-bit.</p></li>
</ol>

<p>All nodes should run kube-proxy. (Running kube-proxy on a “master” node is not strictly required, but being consistent is easier.) Obtain a binary as described for kubelet.</p>

<p>Arguments to consider:</p>

<p>If following the HTTPS security approach:</p>

<pre><code>--master=https://$MASTER_IP
--kubeconfig=/var/lib/kube-proxy/kubeconfig
</code></pre>

<p>Otherwise, if taking the firewall-based security approach</p>

<pre><code>--master=http://$MASTER_IP
</code></pre>

<p>Note that on some Linux platforms, you may need to manually install the conntrack package which is a dependency of kube-proxy, or else kube-proxy cannot be started successfully.</p>

<p>For more details on debugging kube-proxy problems, please refer to Debug Services</p>

<p>Source : <a href="https://kubernetes.io/docs/getting-started-guides/scratch/#kube-proxy" rel="nofollow noreferrer">https://kubernetes.io/docs/getting-started-guides/scratch/#kube-proxy</a></p>
