<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cluster Management on Support Tools</title><link>https://support.tools/categories/cluster-management/</link><description>Recent content in Cluster Management on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 16 Sep 2024 19:26:00 -0500</lastBuildDate><atom:link href="https://support.tools/categories/cluster-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Install Kubernetes Dashboard</title><link>https://support.tools/install-kubernetes-dashboard/</link><pubDate>Mon, 16 Sep 2024 19:26:00 -0500</pubDate><guid>https://support.tools/install-kubernetes-dashboard/</guid><description>&lt;p&gt;The Kubernetes Dashboard is a web-based user interface that allows you to manage and monitor your Kubernetes cluster. It provides a simplified way to view your cluster’s resources, troubleshoot issues, and perform basic management tasks. In this guide, we’ll walk you through how to install the Kubernetes Dashboard and configure access to it.&lt;/p&gt;</description></item><item><title>Kubernetes Events: How to Keep Historical Data of Your Cluster Elasticsearch</title><link>https://support.tools/post/kubernetes-events-how-to-keep-historical-data-of-your-cluster/</link><pubDate>Thu, 13 Oct 2022 09:30:00 -0500</pubDate><guid>https://support.tools/post/kubernetes-events-how-to-keep-historical-data-of-your-cluster/</guid><description>&lt;h2 id="kubernetes-events-how-to-keep-historical-data-of-your-cluster"&gt;Kubernetes Events: How to Keep Historical Data of Your Cluster&lt;/h2&gt;&#10;&lt;p&gt;Are you running a Kubernetes cluster in production? If so, you&amp;rsquo;ve likely encountered unexpected issues that can disrupt your applications. Recently, I had a production application POD crash, and it took me hours to discover that it was OOMKilled. Surprisingly, I couldn&amp;rsquo;t find relevant information when running the kubectl event command.&lt;/p&gt;&#10;&lt;p&gt;I later discovered that Kubernetes only retains event history for a mere 1 hour by default. While you can customize this by tweaking the kube-apiserver with a special flag, most clusters stick with the default setting:&lt;/p&gt;</description></item></channel></rss>