add-image-updater

Generate ArgoCD ImageUpdater YAML for digest-based image updates.

5|Updated Aug 26, 2024
One-click install
npx skills add https://github.com/jomcgi/homelab --skill add-image-updater
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-image-updater
Source: https://github.com/jomcgi/homelab/tree/main/.claude/skills/add-image-updater
Command: npx skills add https://github.com/jomcgi/homelab --skill add-image-updater

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and management of ArgoCD ImageUpdater resources to maintain digest-based updates for container images in a Helm/Overlay-based deployment workflow.

Core Features & Use Cases

  • Automatically generates an imageupdater.yaml in overlays/<env>/<service>/ with a digest update strategy.
  • Configures applicationRefs, manifestTargets, and writeBackTarget to enable Git-based value updates and automatic deployment rollouts.
  • Supports common deployment patterns across Helm charts and Kubernetes overlays, with guidance for typical environments.

Quick Start

Run /add-image-updater <service-name> [image-pattern] to create an ImageUpdater resource for your service.

Frequently Asked Questions about add-image-updater

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate ArgoCD image updates by digest in Kubernetes?

ArgoCD image updates by digest are automated by generating an ImageUpdater resource with a digest update strategy. This synchronizes service images with registry digests and configures Git write-backs to update Helm values across overlays.

How do I configure ArgoCD ImageUpdater writeBackTarget paths for Helm overlays?

Configuring ArgoCD ImageUpdater writeBackTarget paths involves computing the correct relative directory path within your repository. The generated imageupdater.yaml is placed in overlays/<env>/<service>/ to enable Git-based value updates.

Does ArgoCD ImageUpdater work with Helm charts and Kubernetes overlays across multiple environments?

ArgoCD ImageUpdater works with Helm charts and Kubernetes overlays across multiple environments. It configures applicationRefs and manifestTargets to coordinate automatic deployment rollouts for services managed by ArgoCD.

Can I automatically roll out new container image digests to ArgoCD deployments via Git write-back?

New container image digests can be rolled out to ArgoCD deployments via Git write-back. The ImageUpdater applies a digest update strategy that writes synchronized Helm values back to your Git repository, triggering automatic deployment rollouts.

Why does my ArgoCD ImageUpdater fail to write Helm values back to the correct overlay path?

ArgoCD ImageUpdater Git write-back failures often stem from an incorrect relative writeBackTarget path. The resource must compute the precise repository path to successfully write updated Helm values to the intended overlays/<env>/<service>/ directory.