argocd

Coordinate ArgoCD deployments on K3s for branch smoke tests and OCI chart pinning.

32|5|Updated Oct 6, 2024
One-click install
npx skills add https://github.com/gilesknap/tpi-k3s-ansible --skill argocd-gilesknap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: argocd
Source: https://github.com/gilesknap/tpi-k3s-ansible/tree/main/.claude/skills/argocd
Command: npx skills add https://github.com/gilesknap/tpi-k3s-ansible --skill argocd-gilesknap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates ArgoCD operations on a K3s cluster to streamline branch testing and correct OCI chart wiring for app-of-apps deployments.

Core Features & Use Cases

  • Branch repointing workflow for PR smoke tests: update the repo_branch locally, re-template the root application, and refresh as needed.
  • OCI Helm charts handling: ensure bare repo URLs and sourceRepos match to avoid OCI prefix pitfalls when pinning versions.
  • Controller and revalidation guidance: bounce the ArgoCD controller and re-validate to recover from changes.

Quick Start

Smoke-test a PR by updating group_vars/all.yml with repo_branch, then run the cluster play to re-template the root application, and if necessary force a hard refresh of the root to pick up the new revision.

Frequently Asked Questions about argocd

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

FAQPage Schema
How do I repoint an ArgoCD app-of-apps deployment to a PR branch for smoke testing?

To repoint an ArgoCD app-of-apps deployment for branch smoke testing, update the repo_branch in your group variables, re-template the root application, and force a hard refresh so ArgoCD picks up the new revision.

Why are my ArgoCD OCI Helm charts failing to pin versions correctly?

ArgoCD OCI Helm chart pinning fails when bare repository URLs and sourceRepos do not match. Ensure you use bare repo URLs without OCI prefixes to avoid source repository matching pitfalls during version pinning.

How do I troubleshoot ArgoCD application propagation when changes are not syncing?

To troubleshoot ArgoCD app propagation failures, bounce the ArgoCD controller to clear stale state, then re-validate the application sync status to ensure the app-of-apps setup correctly propagates changes.

Does this ArgoCD workflow require a specific Kubernetes distribution like K3s?

This ArgoCD workflow is coordinated specifically for K3s clusters. It enforces explicit branching, OCI URL conventions, and revalidation steps to keep ArgoCD deployments in sync within that environment.

What is the best way to manage Helm chart versions in an ArgoCD app-of-apps setup?

The best way to manage Helm chart versions in an ArgoCD app-of-apps setup is to enforce OCI URL conventions, ensuring bare repository URLs match sourceRepos exactly to avoid prefix pitfalls when pinning chart versions.