<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Finalizers on Support Tools</title><link>https://support.tools/tags/finalizers/</link><description>Recent content in Finalizers on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 03 Dec 2024 21:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/tags/finalizers/index.xml" rel="self" type="application/rss+xml"/><item><title>Rancher and CAPI Finalizers: Managing Kubernetes Clusters Effectively</title><link>https://support.tools/rancher-capi-finalizers/</link><pubDate>Tue, 03 Dec 2024 21:00:00 -0500</pubDate><guid>https://support.tools/rancher-capi-finalizers/</guid><description>&lt;p&gt;Rancher and Cluster API (CAPI) are powerful tools for managing Kubernetes clusters, from provisioning to lifecycle management. Both frameworks rely heavily on &lt;strong&gt;finalizers&lt;/strong&gt; to coordinate resource cleanup and ensure that no dangling dependencies or orphaned infrastructure remain after a resource is deleted. In this post, we’ll explore how Rancher and CAPI use finalizers, what happens during cluster deletion, common pitfalls, and best practices for handling stuck finalizers.&lt;/p&gt;</description></item></channel></rss>