<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Configmap on Support Tools</title><link>https://support.tools/tags/configmap/</link><description>Recent content in Configmap on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 05 Jun 2025 00:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/tags/configmap/index.xml" rel="self" type="application/rss+xml"/><item><title>Runtime Environment Variables with React, Kubernetes, and Apache</title><link>https://support.tools/react-runtime-config-k8s/</link><pubDate>Thu, 05 Jun 2025 00:00:00 -0500</pubDate><guid>https://support.tools/react-runtime-config-k8s/</guid><description>&lt;p&gt;Building React apps once and deploying them across multiple environments—without rebuilding—is a common challenge. Most frontend apps hardcode environment variables at build time, meaning any change (like an API URL or login redirect) requires a full rebuild and redeploy. That’s slow, error-prone, and breaks the Twelve-Factor App principle of separating config from code.&lt;/p&gt;&#10;&lt;p&gt;In this guide, I’ll show you how to configure React environment variables &lt;strong&gt;at runtime&lt;/strong&gt; using Apache and Kubernetes, enabling you to use the same Docker image across &lt;code&gt;dev&lt;/code&gt;, &lt;code&gt;staging&lt;/code&gt;, and &lt;code&gt;production&lt;/code&gt;.&lt;/p&gt;</description></item><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><item><title>Change Default HTTP Port for Bitnami/nginx Web Server Using ConfigMap in Kubernetes</title><link>https://support.tools/change-nginx-port-configmap-kubernetes/</link><pubDate>Sat, 12 Oct 2024 19:26:00 -0500</pubDate><guid>https://support.tools/change-nginx-port-configmap-kubernetes/</guid><description>&lt;p&gt;When running a &lt;strong&gt;Bitnami/nginx web server&lt;/strong&gt; in Kubernetes, you might need to change the default HTTP port (which is typically port 80) to a different port for various reasons, such as security policies, port conflicts, or custom routing requirements. In this post, we’ll show you how to modify the default port of an NGINX web server using a &lt;strong&gt;ConfigMap&lt;/strong&gt; in Kubernetes.&lt;/p&gt;</description></item><item><title>Reload Prometheus ConfigMap without Restarting the Kubernetes Pod</title><link>https://support.tools/reload-prometheus-configmap-kubernetes/</link><pubDate>Wed, 04 Sep 2024 19:26:00 -0500</pubDate><guid>https://support.tools/reload-prometheus-configmap-kubernetes/</guid><description>&lt;p&gt;In Kubernetes, Prometheus configuration changes traditionally require a pod restart to take effect. However, using a configuration reload method, you can avoid downtime and ensure smooth configuration updates.&lt;/p&gt;</description></item></channel></rss>