<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kube-Proxy on Support Tools</title><link>https://support.tools/tags/kube-proxy/</link><description>Recent content in Kube-Proxy on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 01 Apr 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://support.tools/tags/kube-proxy/index.xml" rel="self" type="application/rss+xml"/><item><title>RKE2 the Hard Way: Part 7 – Setting up kubelet and kube-proxy on Worker Nodes</title><link>https://support.tools/training/rke2-hard-way/07-setting-up-kubelet-and-kube-proxy/</link><pubDate>Tue, 01 Apr 2025 00:00:00 +0000</pubDate><guid>https://support.tools/training/rke2-hard-way/07-setting-up-kubelet-and-kube-proxy/</guid><description>&lt;h2 id="part-7--setting-up-kubelet-and-kube-proxy-on-worker-nodes"&gt;Part 7 – Setting up kubelet and kube-proxy on Worker Nodes&lt;/h2&gt;&#10;&lt;p&gt;In this part of the &lt;strong&gt;&amp;ldquo;RKE2 the Hard Way&amp;rdquo;&lt;/strong&gt; training series, we will configure &lt;strong&gt;kubelet&lt;/strong&gt; to register with the Kubernetes API server and set up &lt;strong&gt;kube-proxy&lt;/strong&gt; on our nodes. We already installed containerd and kubelet in &lt;a href="https://support.tools/training/rke2-hard-way/03-setting-up-containerd-and-kubelet/"&gt;Part 3&lt;/a&gt;, but now we need to finalize their configuration to connect to our Kubernetes control plane.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;kubelet&lt;/strong&gt; is the primary node agent that runs on each node. It ensures containers are running in a Pod and healthy.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;kube-proxy&lt;/strong&gt; maintains network rules on nodes. These network rules allow network communication to your Pods from inside or outside of your cluster.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;blockquote&gt;&lt;p&gt;✅ &lt;strong&gt;Note:&lt;/strong&gt; In our setup, all nodes (node01, node02, node03) are both control plane and worker nodes. This is common for smaller clusters and provides high availability without needing separate worker nodes.&lt;/p&gt;&#10;&lt;/blockquote&gt;</description></item><item><title>Deep Dive: Kubernetes Proxy (kube-proxy)</title><link>https://support.tools/training/kubernetes-deep-dive/kube-proxy/</link><pubDate>Wed, 01 Jan 2025 00:00:00 -0500</pubDate><guid>https://support.tools/training/kubernetes-deep-dive/kube-proxy/</guid><description>&lt;p&gt;Kube-proxy is responsible for implementing the Kubernetes Service concept, providing network proxying and load balancing. This deep dive explores its architecture, proxy modes, and internal workings.&lt;/p&gt;</description></item></channel></rss>