<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Helm on Support Tools</title><link>https://support.tools/categories/helm/</link><description>Recent content in Helm on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 19 Feb 2025 18:30:00 -0500</lastBuildDate><atom:link href="https://support.tools/categories/helm/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting Up Harbor Registry on Kubernetes Using Helm Chart</title><link>https://support.tools/setting-up-harbor-registry-kubernetes-helm/</link><pubDate>Wed, 19 Feb 2025 18:30:00 -0500</pubDate><guid>https://support.tools/setting-up-harbor-registry-kubernetes-helm/</guid><description>&lt;p&gt;Are you looking to set up a secure and efficient container image registry on your Kubernetes cluster? &lt;strong&gt;Harbor&lt;/strong&gt; is an open-source container image registry that enhances security and performance with features like role-based access control, vulnerability scanning, and image signing. In this guide, we&amp;rsquo;ll walk you through the steps to deploy Harbor on Kubernetes using Helm charts.&lt;/p&gt;</description></item><item><title>How to Use One Helm Chart for EKS and GKE</title><link>https://support.tools/use-one-helm-chart-eks-gke/</link><pubDate>Thu, 17 Oct 2024 19:26:00 -0500</pubDate><guid>https://support.tools/use-one-helm-chart-eks-gke/</guid><description>&lt;p&gt;As Kubernetes grows in popularity, many organizations are deploying clusters across multiple cloud providers like &lt;strong&gt;Amazon EKS (Elastic Kubernetes Service)&lt;/strong&gt; and &lt;strong&gt;Google GKE (Google Kubernetes Engine)&lt;/strong&gt;. Managing applications across these environments can become complex, especially when dealing with cloud-specific configurations. &lt;strong&gt;Helm&lt;/strong&gt; provides an excellent way to standardize deployments, but how can you create a single Helm chart that works for both EKS and GKE?&lt;/p&gt;&#10;&lt;p&gt;In this post, we’ll explore how to configure one Helm chart to deploy your applications on both &lt;strong&gt;EKS&lt;/strong&gt; and &lt;strong&gt;GKE&lt;/strong&gt; by using cloud-specific values and conditionals.&lt;/p&gt;</description></item><item><title>Reusing Existing Kubernetes Secrets in Helm Templates</title><link>https://support.tools/reusing-kubernetes-secrets-helm-templates/</link><pubDate>Mon, 07 Oct 2024 19:26:00 -0500</pubDate><guid>https://support.tools/reusing-kubernetes-secrets-helm-templates/</guid><description>&lt;p&gt;Kubernetes Secrets are an essential part of securing sensitive information such as passwords, API keys, and certificates. When using Helm to manage your Kubernetes deployments, there are often cases where you need to reuse existing Secrets rather than creating new ones. This is a common requirement in scenarios where Secrets are managed externally or shared across multiple applications.&lt;/p&gt;&#10;&lt;p&gt;In this post, we will explore how to reuse existing Kubernetes Secrets within your Helm templates, ensuring efficient management and security for your workloads.&lt;/p&gt;</description></item></channel></rss>