The Ultimate Guide to Upgrading Helm Charts in Your Kubernetes Cluster

8 August 2024

Using Multiple Versions of Helm Charts in a Single Cluster

When managing applications on Kubernetes using Helm Charts, it’s often necessary to upgrade them. However, this process can be complex due to the potential for version conflicts between charts and their dependencies. This complexity is further exacerbated by the requirement for minimal downtime.
One strategy to consider when upgrading Helm Charts is to utilize multiple versions of a chart in your cluster simultaneously. This approach allows you to upgrade one version while still running another. However, this technique requires careful planning, especially regarding how to handle different versions’ dependencies and resources.

Strategy for Upgrading with Multiple Versions

To execute an upgrade using multiple versions, follow these steps:

Create Separate Configurations: Before upgrading, create separate configurations for each chart version you intend to use. This step is crucial as it helps in distinguishing between the different versions of your charts.
Define Release Names: When configuring Helm releases for each version, make sure to specify unique release names. This can help prevent conflicts and ensure that upgrades are applied correctly to specific versions.
Use Version-Specific Values: Use values.yaml files or similar configuration mechanisms to define different settings for each chart version. This approach allows you to tailor configurations based on the specific requirements of your applications at various stages.
Implement Upgrade Mechanisms: To automate upgrades between versions, you can create scripts or jobs that use Helm’s built-in upgrade functionality. These upgrades should be designed with minimal downtime in mind, possibly leveraging rolling updates if applicable.

Handling Dependencies and Resources

When managing multiple versions of a chart, dependencies and resources become critical considerations. Ensure that you have a clear strategy for handling these aspects:

Resource Allocation: Allocate specific resources for each chart version as needed. This step is essential to prevent conflicts over resources like memory or CPU.
Dependency Management: Use tools like Helm Charts’ built-in dependency management features or external packages to manage dependencies between versions.

Conclusion

Upgrading Helm Charts in a Kubernetes cluster can be complex due to the potential for version conflicts and the need for minimal downtime. Using multiple versions of a chart simultaneously is one strategy to consider, but it requires careful planning regarding how to handle different versions’ dependencies and resources. By following the steps outlined above and implementing a clear upgrade mechanism, you can ensure smooth transitions between chart versions.

Step-by-Step Example

Here’s an example of how you might use Helm Charts with multiple versions in your cluster:

Step 1: Create Separate Configurations

helm create v1-chart
helm create v2-chart

Step 2: Define Release Names

# v1-values.yaml
name: v1-app

image:
  repository: example/v1-app
  tag: latest

# v2-values.yaml
name: v2-app

image:
  repository: example/v2-app
  tag: latest

Step 3: Use Version-Specific Values

helm install v1-chart v1-values.yaml --name v1-release
helm install v2-chart v2-values.yaml --name v2-release

Step 4: Implement Upgrade Mechanisms

helm upgrade v1-release v1-chart v1-values.yaml
helm upgrade v2-release v2-chart v2-values.yaml

Poespas Blog