<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Static Pods on Support Tools</title><link>https://support.tools/tags/static-pods/</link><description>Recent content in Static Pods 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/static-pods/index.xml" rel="self" type="application/rss+xml"/><item><title>RKE2 the Hard Way: Part 4 – Setting up etcd Cluster as Static Pods</title><link>https://support.tools/training/rke2-hard-way/04-setting-up-etcd-cluster/</link><pubDate>Tue, 01 Apr 2025 00:00:00 +0000</pubDate><guid>https://support.tools/training/rke2-hard-way/04-setting-up-etcd-cluster/</guid><description>&lt;h2 id="part-4--setting-up-etcd-cluster-as-static-pods"&gt;Part 4 – Setting up etcd Cluster as Static Pods&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 set up &lt;strong&gt;etcd&lt;/strong&gt; as a clustered key-value store using &lt;strong&gt;static pods&lt;/strong&gt; managed by kubelet. etcd is a consistent and highly-available key-value store used by Kubernetes to store all cluster data, including the state of the cluster, configuration data, and metadata.&lt;/p&gt;&#10;&lt;p&gt;In RKE2, etcd is deployed as a static pod managed by kubelet, instead of running directly as a systemd service. This makes it easier to manage, as kubelet handles lifecycle operations, restarts, and monitoring.&lt;/p&gt;</description></item><item><title>RKE2 the Hard Way: Part 5 – Setting up kube-apiserver as Static Pods</title><link>https://support.tools/training/rke2-hard-way/05-setting-up-kube-apiserver/</link><pubDate>Tue, 01 Apr 2025 00:00:00 +0000</pubDate><guid>https://support.tools/training/rke2-hard-way/05-setting-up-kube-apiserver/</guid><description>&lt;h2 id="part-5--setting-up-kube-apiserver-as-static-pods"&gt;Part 5 – Setting up kube-apiserver as Static Pods&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 set up the &lt;strong&gt;Kubernetes API Server&lt;/strong&gt; (&lt;code&gt;kube-apiserver&lt;/code&gt;) as static pods managed by kubelet on each of our nodes. The API server is the central component of the Kubernetes control plane that exposes the Kubernetes API.&lt;/p&gt;&#10;&lt;p&gt;Using static pods for the API server is a key design principle in RKE2. This approach simplifies deployment and management, as kubelet will automatically start the API server and ensure it stays running. If an API server instance fails, kubelet will automatically restart it.&lt;/p&gt;</description></item><item><title>RKE2 the Hard Way: Part 6 – Setting up kube-controller-manager and kube-scheduler as Static Pods</title><link>https://support.tools/training/rke2-hard-way/06-setting-up-kube-controller-manager-and-kube-scheduler/</link><pubDate>Tue, 01 Apr 2025 00:00:00 +0000</pubDate><guid>https://support.tools/training/rke2-hard-way/06-setting-up-kube-controller-manager-and-kube-scheduler/</guid><description>&lt;h2 id="part-6--setting-up-kube-controller-manager-and-kube-scheduler-as-static-pods"&gt;Part 6 – Setting up kube-controller-manager and kube-scheduler as Static Pods&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 set up the &lt;strong&gt;Kubernetes Controller Manager&lt;/strong&gt; (&lt;code&gt;kube-controller-manager&lt;/code&gt;) and &lt;strong&gt;Scheduler&lt;/strong&gt; (&lt;code&gt;kube-scheduler&lt;/code&gt;) as static pods managed by kubelet on each of our nodes.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;The Controller Manager runs controller processes that regulate the state of the cluster (such as replication controllers, node controllers, and service account controllers)&lt;/li&gt;&#10;&lt;li&gt;The Scheduler is responsible for watching for newly created pods and assigning them to nodes&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Using static pods for these components is a key design principle in RKE2, just like we did for etcd and kube-apiserver. This approach ensures high availability and automatic recovery in case of failures.&lt;/p&gt;</description></item></channel></rss>