<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Muthuprakash Gopal on Medium]]></title>
        <description><![CDATA[Stories by Muthuprakash Gopal on Medium]]></description>
        <link>https://medium.com/@muthuprakashgopal?source=rss-f567e111cf53------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8jOzM3gFKmEBrbnv0SMeJQ.png</url>
            <title>Stories by Muthuprakash Gopal on Medium</title>
            <link>https://medium.com/@muthuprakashgopal?source=rss-f567e111cf53------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:25:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@muthuprakashgopal/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A Beginner’s Guide to Helm Charts — Part 2: Installing MiniKube and Hosting a Simple Containerized…]]></title>
            <link>https://medium.com/@muthuprakashgopal/a-beginners-guide-to-helm-charts-part-2-installing-minikube-and-hosting-a-simple-containerized-dee9f99dbda3?source=rss-f567e111cf53------2</link>
            <guid isPermaLink="false">https://medium.com/p/dee9f99dbda3</guid>
            <category><![CDATA[environment]]></category>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[helm]]></category>
            <category><![CDATA[minikube]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Muthuprakash Gopal]]></dc:creator>
            <pubDate>Sat, 03 Jun 2023 14:59:43 GMT</pubDate>
            <atom:updated>2023-06-03T15:01:51.158Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Beginner’s Guide to Helm Charts — Part 2: Installing MiniKube and Hosting a Simple Containerized Application In Multiple Environments</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*hJcAl0uk4QeGR9UFQvRbsQ.png" /></figure><p><strong>Introduction:</strong> In the previous article, we explored the fundamentals of Helm charts and their role in simplifying application deployment. In this second part, we will delve into the installation of MiniKube, a local Kubernetes cluster, and the process of hosting a simple containerized application in multiple environments using Helm charts .</p><p><strong>Installing MiniKube:</strong></p><p>a. Visit the official MiniKube repository at <a href="https://github.com/kubernetes/minikube">https://github.com/kubernetes/minikube</a>.</p><p>b. Follow the installation instructions for your operating system to download and install MiniKube. Or use this direct link to download <a href="https://storage.googleapis.com/minikube/releases/latest/minikube-installer.exe">miniKube .exe for windows</a>.</p><p>c. Ensure that you have a compatible hypervisor installed, such as VirtualBox, KVM, or HyperKit, as MiniKube requires a hypervisor to run Kubernetes locally.</p><p>d. Verify the installation by opening a terminal or command prompt and running the minikube version command. It should display the installed version of MiniKube.</p><p><strong>Setting up Helm:</strong></p><p>a. Visit the official Helm website at <a href="https://helm.sh/">https://helm.sh</a>.</p><p>b. Download the appropriate Helm binary for your operating system and install it following the provided instructions.</p><p>c. Verify the installation by running the helm version command in your terminal or command prompt. It should display the installed version of Helm.</p><p><strong>Creating a Helm Chart for the example application:</strong></p><p>a. In your terminal or command prompt, navigate to the directory where you want to create your Helm chart.</p><p>b. Run the command helm create myapp to create a new Helm chart named “myapp”.</p><p>c. This will generate a basic directory structure for the Helm chart, including templates, values, and charts folders.</p><p><strong>Customizing the Helm Chart for the example application:</strong></p><p>a. Open the values.yaml file in the myapp directory using a text editor.</p><p>b. Modify the values in the values.yaml file to configure the example application. For instance, specify the image repository, ports, environment variables, and other configuration options required for the example app.</p><p>c. Customize the Kubernetes manifest files in the templates directory if necessary to define additional resources or modify existing ones.</p><p><strong>Deploying the example application using Helm:</strong></p><p>a. In your terminal or command prompt, navigate to the directory where your Helm chart is located (myapp in this example).</p><p>b. Run the command helm install myapp-release . to deploy the example application using Helm. Replace “myapp-release” with a name of your choice.</p><p>c. Helm will create a release named “myapp-release” and install the example application based on the configurations defined in your Helm chart.</p><p>d. Verify the deployment by running kubectl get pods to see if the application pods are running successfully.</p><p><strong>Accessing the deployed example application:</strong></p><p>a. To access the deployed example application, obtain the IP address of the MiniKube cluster by running the command minikube ip in your terminal or command prompt.</p><p>b. Determine the exposed port for the example application by running kubectl get services and look for the service associated with your Helm release.</p><p>c. Use the IP address along with the exposed port to access your example application in a web browser or make API requests.</p><p><strong>Understanding Multiple Environments:</strong> When working with complex projects, it’s common to have different environments, such as development, staging, and production. Each environment may have distinct configuration requirements, including database credentials, API endpoints, and resource limits. Helm charts provide a powerful mechanism to manage these variations efficiently.</p><p><strong>Creating Environment-Specific Values Files</strong>: To facilitate deployment across multiple environments, we can leverage the power of values files in Helm. Start by creating separate values files for each environment, such as values-dev.yaml, values-staging.yaml, and values-prod.yaml. These files will contain environment-specific configuration values.</p><p>Example:</p><pre># values-dev.yaml<br>my-app:<br>  replicaCount: 1<br>  image:<br>    repository: my-app<br>    tag: dev<br><br># values-staging.yaml<br>my-app:<br>  replicaCount: 2<br>  image:<br>    repository: my-app<br>    tag: staging<br><br># values-prod.yaml<br>my-app:<br>  replicaCount: 3<br>  image:<br>    repository: my-app<br>    tag: prod</pre><p>This example has three environments — dev, staging and prod — each with a different number of replicas and image tags.</p><p><strong>Customizing Values for Each Environment:</strong> Within each environment-specific values file, customize the configuration values to match the requirements of that environment. For example, you can define different database credentials, adjust resource allocations, and set specific API endpoints. By modifying these values, you can adapt the Helm chart deployment to suit each environment’s needs.</p><p>Using Helm’s --values Flag: To deploy the application for a specific environment, use the --values flag with the helm install command. For instance, execute helm install myapp-release --values values-dev.yaml . to deploy the application with the development environment configuration. Replace values-dev.yaml with the respective values file for the desired environment.</p><p><strong>Automating Environment-Specific Deployments: </strong>To further automate the deployment process, consider using a CI/CD pipeline or deployment scripts. These tools can read the environment-specific values files and automatically deploy the Helm chart based on the target environment. This approach helps ensure consistent deployments and minimizes the risk of human error.</p><p><strong>Managing Environment-Specific Overrides:</strong> In some cases, you may need to override specific values for a particular environment without modifying the original values file. Helm provides a way to accomplish this by using the --set flag. For example, you can execute helm install myapp-release --values values-prod.yaml --set image.tag=v1.2.3 . to override the image tag value specifically for the production environment.</p><p><strong>Conclusion: </strong>Congratulations! You’ve successfully installed MiniKube, set up Helm, and hosted a simple containerized application using Helm charts. In this article, we explored the installation process, customization of Helm charts, and accessing the deployed application. With Helm, managing and deploying applications on Kubernetes becomes significantly easier even for multiple environments.</p><p><strong>FIND ME ON :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/50/1*jmYSmbz5VBbZ1CX1q1ZhNw.gif" /><figcaption><a href="https://sites.google.com/view/muthuprakash/home">Portfolio</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/0*pGopmE-ARke9SJUx.gif" /><figcaption><a href="https://www.linkedin.com/in/muthuprakash-g-30028a212/">LinkedIn</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/50/0*Bhc6P3t4z2KVwQuW.gif" /><figcaption><a href="https://play.google.com/store/apps/dev?id=9216818427339548155&amp;pli=1">Google Play Store</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/50/0*L9xQVWBWMs0cGbML.gif" /><figcaption><a href="https://www.instagram.com/muthuprakash_gopal/">Instagram</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dee9f99dbda3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Beginner’s Guide to Helm Charts: Simplifying Application Deployment]]></title>
            <link>https://medium.com/@muthuprakashgopal/a-beginners-guide-to-helm-charts-simplifying-application-deployment-f47f872825a6?source=rss-f567e111cf53------2</link>
            <guid isPermaLink="false">https://medium.com/p/f47f872825a6</guid>
            <category><![CDATA[helm-chart]]></category>
            <category><![CDATA[package-management]]></category>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Muthuprakash Gopal]]></dc:creator>
            <pubDate>Sun, 21 May 2023 18:38:00 GMT</pubDate>
            <atom:updated>2023-06-03T15:03:33.111Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*L9xLY35cLzAETKH7A7fA_w.png" /></figure><p><strong>Introduction:</strong></p><p>In the world of containerized applications, orchestrating and managing deployments can be a complex task. However, with the emergence of Helm charts, the process of deploying applications has become more streamlined and efficient. In this beginner-level blog, we will explore Helm charts, understand how they simplify application deployment, and discuss their advantages and disadvantages.</p><p><strong>What are Helm Charts?</strong></p><p>Helm is a package manager for Kubernetes that helps in deploying and managing applications. Helm charts, the core component of Helm, provide a templating mechanism to define, package, and deploy applications on Kubernetes clusters. Essentially, a Helm chart is a collection of files that describe the necessary resources, dependencies, and configuration options for an application.</p><p><strong>Simplifying Application Deployment:</strong></p><p>1. Easy Package Management: Helm charts package all the required Kubernetes resources, such as deployments, services, and configmaps, into a single package. This makes it easier to distribute, version, and share applications, enabling easy collaboration between developers.</p><p>2. Templating and Configuration: Helm charts use a templating engine called Go templates, which allows users to define and customize values for different configurations. This enables you to create reusable templates and deploy multiple instances of an application with varying configurations.</p><p>3. Dependency Management: Helm charts can include dependencies, such as other charts or external services, simplifying the deployment of complex applications with interconnected components. Dependencies can be automatically resolved and installed, reducing the manual effort required to manage dependencies.</p><p><strong>Examples:</strong></p><p>Let’s take a look at a simple example to understand how Helm charts work. Suppose we have a web application that consists of a frontend deployment, a backend deployment, and a service for external access. Here’s how we can define this application using a Helm chart:</p><blockquote>```</blockquote><blockquote>myapp/</blockquote><blockquote>├── Chart.yaml</blockquote><blockquote>├── values.yaml</blockquote><blockquote>├── templates/</blockquote><blockquote>│ ├── deployment.yaml</blockquote><blockquote>│ ├── service.yaml</blockquote><blockquote>└───└─── backend/</blockquote><blockquote>├── deployment.yaml</blockquote><blockquote>```</blockquote><p>In the `Chart.yaml` file, we define metadata about the chart, such as the name, version, and dependencies. The `values.yaml` file contains configurable values for the application. The `templates` directory contains the actual Kubernetes resource definitions, written using Go templates.</p><p><strong>How it works:</strong></p><p>Helm works by leveraging the power of Kubernetes to streamline the application deployment process. It follows a client-server architecture, with the Helm client interacting with the Tiller server (prior to Helm 3) or directly with Kubernetes (starting from Helm 3) to manage charts and releases.</p><p>When you use Helm, you start by creating or selecting a Helm chart. A Helm chart is essentially a directory structure containing YAML files that define Kubernetes resources, such as deployments, services, and configmaps, along with other metadata and configuration options.</p><p>The Helm client allows you to interact with the chart, providing commands to install, upgrade, or uninstall releases. It also offers commands to inspect charts, fetch dependencies, and manage repositories.</p><p>During installation, Helm deploys the chart to your Kubernetes cluster. It generates Kubernetes resource manifests based on the chart’s templates and combines them with the configuration values you provide. The templates use the Go templating language, allowing for dynamic rendering and customization of the Kubernetes resource definitions.</p><p>Helm manages releases, which represent instances of deployed applications. Each release has a unique name and tracks the deployed version, configuration, and other details. This enables you to manage and update applications easily, with options for rollbacks, upgrades, and scaling.</p><p>With the release of Helm 3, Tiller, the server-side component of Helm, was removed, and Helm now interacts directly with Kubernetes using the Kubernetes API. This change improved security and simplified the Helm architecture.</p><p>Overall, Helm simplifies application deployment by providing a package manager-like approach, allowing you to package, configure, and manage applications using charts, templates, and configuration values. It abstracts away the complexities of Kubernetes resource management, making it easier to deploy and manage applications on Kubernetes clusters.</p><p><strong>Advantages of Helm Charts:</strong></p><p>1. Reusability: Helm charts promote code reusability by allowing you to define templates and values that can be shared across different deployments, saving time and effort.</p><p>2. Versioning: Helm charts support versioning, enabling easy rollback to previous versions if issues arise during deployment or updates.</p><p>3. Community Support: Helm has a vibrant community that actively contributes and maintains a vast repository of charts, providing a wide range of applications and configurations to choose from.</p><p>4. Scalability: Helm charts allow you to easily scale your applications by defining replica counts and resource limits within the chart templates. This ensures that your application can handle increased traffic and workload demands.</p><p>5. Rollbacks and Upgrades: Helm charts support seamless rollbacks and upgrades of applications. If an update introduces issues or unexpected behavior, you can easily roll back to a previous known working version. Helm manages the release history and allows you to upgrade or downgrade your application with a single command.</p><p>6. Configuration Management: Helm charts provide a convenient way to manage application configurations. By separating the configuration values from the actual chart, you can easily update and modify configurations without modifying the underlying chart files. This makes it easier to maintain different configurations for various environments (e.g., development, staging, production).</p><p><strong>Disadvantages of Helm Charts:</strong></p><p>1. Complexity: Helm charts, especially for complex applications, can have a steep learning curve. Understanding the templating engine, writing and maintaining charts, and managing dependencies can be challenging for beginners.</p><p>2. Compatibility: As Helm charts are specific to Kubernetes, using them outside a Kubernetes environment might not be possible. This restricts their usage for non-Kubernetes deployments.</p><p><strong>Conclusion:</strong></p><p>Helm charts have revolutionized the deployment process by simplifying the packaging, configuration, and management of applications on Kubernetes. They offer a standardized and reusable approach, making it easier to deploy complex applications while benefiting from the vast Helm community. Although Helm charts have certain complexities and limitations, they remain an essential tool for modern application deployment in the Kubernetes ecosystem.</p><p>So, dive into Helm charts, experiment with different applications, and experience the power of simplified deployment in your Kubernetes journey.</p><p>And we will discuss more about helm chart implementation in <a href="https://medium.com/@muthuprakashgopal/a-beginners-guide-to-helm-charts-part-2-installing-minikube-and-hosting-a-simple-containerized-dee9f99dbda3">Part-2</a>.<br><a href="https://medium.com/@muthuprakashgopal/a-beginners-guide-to-helm-charts-part-2-installing-minikube-and-hosting-a-simple-containerized-dee9f99dbda3">click here to view the next part</a>.</p><p>FIND ME ON :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/50/1*jmYSmbz5VBbZ1CX1q1ZhNw.gif" /><figcaption><a href="https://sites.google.com/view/muthuprakash/home">Portfolio</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/1*8CkFJ89mqxFb1C8k5498TA.gif" /><figcaption><a href="https://www.linkedin.com/in/muthuprakash-g-30028a212/">LinkedIn</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/50/1*cxUBa1kbCowMy5MLXQohig.gif" /><figcaption><a href="https://play.google.com/store/apps/dev?id=9216818427339548155&amp;pli=1">Google Play Store</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/50/1*l7tsZiqKbqavvSqe-_V0kw.gif" /><figcaption><a href="https://www.instagram.com/muthuprakash_gopal/">Instagram</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f47f872825a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>