K@zuki.

Posted on May 5, 2023 • Updated on May 8, 2023

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

#argo #renovate #devops #kubernetes

Yesterday, I posted an article titled "Automatically Updating Helm Chart Referenced in Argo CD Using Renovate."

Automatically Updating Helm Charts Referenced by Argo CD with Renovate

K@zuki. ・ May 4 ・ 2 min read

#argocd #renovate #devops #kubernetes

That method used regexManagers to retrieve version information from GitHub releases specified in the configuration. However, this time I will introduce an even easier and simpler method.

Recap of Previous Method

The previous method involved adding regexManagers and comments to the lines to be updated.

  // renovate.json5
  "regexManagers": [
    {
      "datasourceTemplate": "github-releases",
      "fileMatch": [
        "argocd-config/base/.*\\.yaml"
      ],
      "matchStrings": [
        // e.g.) targetRevision: 5.31.0 # renovate: depName=argoproj/argo-helm extractVersion=^argo-cd-(?<version>.+)$
        " +targetRevision: +(?<currentValue>[^'\" ]+) +# renovate: depName=(?<depName>[^ \\n]+) +(extractVersion=(?<extractVersion>[^\\n]+))?",
      ],
    },
  ]

# Add comments to the lines to be updated
targetRevision: 5.31.0 # renovate: depName=argoproj/argo-helm extractVersion=^argo-cd-(?<version>.+)$

This time, we will make the automatic update process even easier.

Making It Easier

Read the Documentation

To make the automatic update process even easier, we first read the documentation for Managers.

docs.renovatebot.com

The reason for reading the documentation for Managers is that if there are already suitable Managers listed in the documentation, then you can simply write the configuration for that Manager and it will automatically become an update target.

If it is not listed, then write regexManagers, create an issue, or submit a pull request.

Looking through the documentation, it seems that there is a Manager called argocd.

docs.renovatebot.com

Although it is not clear whether it can be used as is, the Additional Information section suggests that it may be suitable for Argo CD applications.

The argocd manager has no fileMatch default patterns, so it won't match any files until you configure it with a pattern. This is because there is no commonly accepted file/directory naming convention for argocd YAML files and we don't want to check every single *.yaml file in repositories just in case any of them have ArgoCD definitions.

Define the Configuration

If there is a definition for regexManagers, delete it. Simply define the path to the files to be updated in fileMatch.

  "argocd": {
    "fileMatch": [
      "argocd-config/base/.*\\.yaml",
    ],
  },

FYI: https://github.com/corrupt952/home-apps/blob/main/.github/renovate.json5#L19-L23

Updating the configuration in this way will make it an update target. It is much simpler than the previous method.

PRs Created

chore(deps): update helm release argo-cd to v5.31.1 #39

renovate[bot] posted on May 05, 2023

This PR contains the following updates:

Package	Update	Change
argo-cd	patch	`5.31.0` -> `5.31.1`

Release Notes

argoproj/argo-helm

Automatically Updating Helm Charts Referenced by Argo CD with Renovate

K@zuki. ・ May 4 ・ 2 min read

Recap of Previous Method

Making It Easier

Read the Documentation

Define the Configuration

PRs Created

Release Notes

Configuration

Configuration

Release Notes

Configuration

Configuration

Configuration

Conclusion

Read next

Quick tutorial: How to add a release GitHub workflow

Exploring Pkl: Apple's Fresh Approach to Configuration Languages

Top DevOps Secret Best Practices That No One Tells

DevSecOps 101: What is DevSecOps?