<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dynamic on Support Tools</title><link>https://support.tools/tags/dynamic/</link><description>Recent content in Dynamic on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 16 Oct 2024 19:26:00 -0500</lastBuildDate><atom:link href="https://support.tools/tags/dynamic/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes Static vs Dynamic ConfigMaps</title><link>https://support.tools/kubernetes-static-vs-dynamic-configmaps/</link><pubDate>Wed, 16 Oct 2024 19:26:00 -0500</pubDate><guid>https://support.tools/kubernetes-static-vs-dynamic-configmaps/</guid><description>&lt;p&gt;In Kubernetes, &lt;strong&gt;ConfigMaps&lt;/strong&gt; provide a way to decouple configuration data from containerized applications, allowing you to modify application behavior without rebuilding or redeploying the container images. There are two primary types of ConfigMaps you can use to manage application configurations: &lt;strong&gt;Static ConfigMaps&lt;/strong&gt; and &lt;strong&gt;Dynamic ConfigMaps&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;In this post, we’ll explore the differences between static and dynamic ConfigMaps and how to effectively use them in your Kubernetes environment.&lt;/p&gt;</description></item></channel></rss>