K@zuki.

Posted on May 4, 2023 • Edited on May 5, 2023

Automatically Updating Helm Charts Referenced by Argo CD with Renovate

#argocd #renovate #devops #kubernetes

You can define it more easily in the new article.

Automatically Updating Helm Chart Referenced in Argo CD Using Renovate - Part 2

K@zuki. ・ May 5 '23

#argo #renovate #devops #kubernetes

Introduction

The manifests repo for my home k8s cluster, home-apps, is managed by Argo CD, and each application creates resources using Helm Charts.

However, it is a hassle to manually update them during updates.

Therefore, I will use Renovate to automate the updates.

Setting up Renovate

You can automatically update applications using Renovate.

Refer to the official documentation to set up Renovate.

docs.renovatebot.com

You will need to:

Install and configure Renovate's GitHub App
Merge the PR for the added Renovate configuration file

Once installed, you can check it on Renovate's dashboard.

Manifest Configuration

Before moving on to automatic upgrades, let me briefly introduce the configuration of the manifests repo.
Each manifest in the repo is configured as follows.



argocd-config
└── base
    ├── argocd.yaml
    ├── ingress-nginx.yaml
    ├── kustomization.yaml
    ├── metallb.yaml
    └── sealed-secrets.yaml

Each file defines resources using Helm Charts.
The following is an excerpt from argocd.yaml.



---
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: argocd
spec:
  ...
  source:
    chart: argo-cd
    repoURL: https://argoproj.github.io/argo-helm
    targetRevision: 5.31.0
    helm:
    ...

Automatic Upgrade

You can use Renovate's regexManagers to upgrade.

I don't like to write regexManagers for each application, so I specify the target repository and the release tag format as follows.



targetRevision: 5.31.0 # renovate: depName=argoproj/argo-helm extractVersion=^argo-cd-(?<version>.+)$

Target repository
Release tag format

Specify them as Renovate's update targets.

Release Tag Format

Since many Helm Charts managed by each repository have a prefix, the release tag of each repository contains not only the version string specified in targetRevision, but also a prefix.

The format of the release tags for each repository is as follows.

Argo CD … argo-cd-{VERSION}
Ingress NGINX Controller … helm-chart-{VERSION}
Sealed Secrets … helm-v{VERSION}
MetalLB … metallb-chart-{VERSION}

Define regexManagers

Based on this information, define regexManagers.



  "regexManagers": [
    {
      "datasourceTemplate": "github-releases",
      "fileMatch": [
        "argocd-config/base/.*\\.yaml"
      ],
      "matchStrings": [
        " +targetRevision: +(?<currentValue>[^'\" ]+) +# renovate: depName=(?<depName>[^ \\n]+) +(extractVersion=(?<extractVersion>[^\\n]+))?",
      ],
    },
  ]

Simply adding this definition will make the version of the Helm Charts in the manifest automatically updated.

Created PRs

The following PRs were created by the regexManagers defined this time and became as expected.

chore(deps): update dependency kubernetes/ingress-nginx to v4.6.0 #24

renovate[bot] posted on May 03, 2023

This PR contains the following updates:

Package	Update	Change
kubernetes/ingress-nginx	minor	`4.3.0` -> `4.6.0`

Release Notes

kubernetes/ingress-nginx

Automatically Updating Helm Chart Referenced in Argo CD Using Renovate - Part 2

K@zuki. ・ May 5 '23

Introduction

Setting up Renovate

Manifest Configuration

Automatic Upgrade

Release Tag Format

Define regexManagers

Created PRs

Release Notes

Configuration

Release Notes

Configuration

Release Notes

Configuration

Release Notes

Configuration

Conclusion

Reference

aquaproj / aqua-renovate-config

Renovate Configuration to update packages and registries of aqua

aqua-renovate-config

Document

Contributing

License

Read next

Enhanced Observability for Amazon EKS with CloudWatch Container Insights

How To Add The Whitelist for Your Ingress-Nginx Controller of K8S?

Azure Portal Overview: The Gateway to Cloud Excellence

Key DevOps Trends in 2025