<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubelet on Support Tools</title><link>https://support.tools/tags/kubelet/</link><description>Recent content in Kubelet on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 19 Jun 2025 09:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/tags/kubelet/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes v1.33: Critical Security Fix for Private Image Pull Vulnerability</title><link>https://support.tools/kubernetes-v1-33-security-image-pull-credential-validation/</link><pubDate>Thu, 19 Jun 2025 09:00:00 -0500</pubDate><guid>https://support.tools/kubernetes-v1-33-security-image-pull-credential-validation/</guid><description>&lt;p&gt;Kubernetes v1.33 delivers a vital security enhancement that resolves a decade-old vulnerability in how private container images are accessed. This fix—addressing issue &lt;a href="https://github.com/kubernetes/kubernetes/issues/18787"&gt;#18787&lt;/a&gt;—closes a security loophole that could allow unauthorized workloads to access cached private images without proper authentication.&lt;/p&gt;</description></item><item><title>RKE2 the Hard Way: Part 3 – Setting up containerd and kubelet</title><link>https://support.tools/training/rke2-hard-way/03-setting-up-containerd-and-kubelet/</link><pubDate>Tue, 01 Apr 2025 00:00:00 +0000</pubDate><guid>https://support.tools/training/rke2-hard-way/03-setting-up-containerd-and-kubelet/</guid><description>&lt;h2 id="part-3--setting-up-containerd-and-kubelet"&gt;Part 3 – Setting up containerd and kubelet&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 install and configure &lt;strong&gt;containerd&lt;/strong&gt; (the container runtime) and &lt;strong&gt;kubelet&lt;/strong&gt; (the Kubernetes node agent) on all our nodes. These components form the foundation of our Kubernetes cluster.&lt;/p&gt;&#10;&lt;p&gt;One of the key design decisions in RKE2 is to run the Kubernetes control plane components (etcd, kube-apiserver, kube-controller-manager, and kube-scheduler) as static pods managed by kubelet, rather than as systemd services. This approach simplifies deployment and maintenance, as kubelet manages the lifecycle of these critical components.&lt;/p&gt;</description></item><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 Kubelet</title><link>https://support.tools/training/kubernetes-deep-dive/kubelet/</link><pubDate>Wed, 01 Jan 2025 00:00:00 -0500</pubDate><guid>https://support.tools/training/kubernetes-deep-dive/kubelet/</guid><description>&lt;p&gt;The Kubelet is the primary node agent in Kubernetes, responsible for managing containers and maintaining node state. This deep dive explores its architecture, container lifecycle management, and internal operations.&lt;/p&gt;</description></item><item><title>Configure Kubelet Out of Resource Handling, or How to Stop EKS Kubernetes Nodes from Going Down</title><link>https://support.tools/configure-kubelet-out-of-resource-handling-eks-nodes/</link><pubDate>Sun, 15 Sep 2024 19:26:00 -0500</pubDate><guid>https://support.tools/configure-kubelet-out-of-resource-handling-eks-nodes/</guid><description>&lt;p&gt;Managing resources effectively in Kubernetes is essential to avoid node crashes and resource starvation issues, especially in cloud environments like AWS EKS. Kubelet provides out-of-resource management capabilities that allow you to define eviction thresholds and reserve resources for system daemons, ensuring your EKS worker nodes remain operational.&lt;/p&gt;&#10;&lt;p&gt;In this post, we’ll explore how to configure Kubelet’s out-of-resource handling for EKS worker nodes using Amazon’s EKS-optimized AMI and Terraform.&lt;/p&gt;</description></item></channel></rss>