manage

Files (2)

• SKILL.md
• install-cli.sh · scripts/

SKILL.md (first lines)

## Codex execution

Before shell examples, set PLUGIN_ROOT to the absolute installed plugin directory: two parent directories above this SKILL.md’s containing skill directory. Derive it from the loaded file path, never the working directory. This variable is not automatically supplied to ordinary shell tools. Quote it in commands.

# ArgoCD Skill

This skill allows the agent to interact with ArgoCD using the `argocd` CLI tool,
as well as create Declarative GitOps configurations.

Verify against the canonical docs (https://argo-cd.readthedocs.io/en/stable/)
when being wrong would mislead, and check the server version with
`argocd version` before relying on a field or flag.

## Tool Setup

The `argocd` CLI might need to be downloaded if not present. The installation script downloads
the current stable release into the working directory and verifies it against the release's
`cli_checksums.txt`:

```bash
bash "${PLUGIN_ROOT}/skills/manage/scripts/install-cli.sh"
sudo mv argocd /usr/local/bin/
```

Or you can use Homebrew on macOS:

```bash
brew install argocd
```

## Basic CLI Commands

- Login: `argocd login <SERVER>` (Needs initial password `argocd admin initial-password -n argocd` or other configuration)
- List apps: `argocd app list`
- Get app status: `argocd app get <app-name>`
- Sync an app: `argocd app sync <app-name>`
- Create app (CLI): `argocd app create <name> --repo <repo> --path <path> --dest-server <server> --dest-namespace <namespace>`
- Create project: `argocd proj create <project-name> -d <server>,<namespace> -s <repo>`

## Declarative Setup

ArgoCD configurations are often applied as Custom Resources (CRs) using `kubectl apply`.

### Application Definition

```yaml
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: guestbook
  namespace: argocd
spec:
  project: default
  source:
    repoURL: https://github.com/argoproj/argocd-example-apps.git
    targetRevision: HEAD
    path: guestbook
  destination:
    server: https://kubernetes.default.svc
    namespace: guestbook
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
```

### Tool support: Kustomize

When the source path has a `kustomization.yaml`, ArgoCD detects it as a Kustomize application.
You can set parameters such as inline `patches` (Argo CD v2.9+) in the `Application` spec:

```yaml
  source:
    path: kustomize-guestbook
    repoURL: https://github.com/argoproj/argocd-example-apps.git
    targetRevision: master
    kustomize:
      patches:
        - target:
            kind: Deployment
            name: guestbook-ui
          patch: |-
            - op: replace
              path: /spec/template/spec/containers/0/ports/0/containerPort
              value: 443
```

`kustomize.version: <version>` selects a non-bundled Kustomize. It only works when that binary
is added to the Argo CD image and registered in `argocd-cm` as `kustomize.path.<version>`
(for example `kustomize.path.v3.5.4: /custom-tools/kustomize_3_5_4`). Argo CD v3.5.3 bundles
Kustomize 5.8.1; omit `version` to use it.

### Tool support: Helm

Helm charts can be passed parameters via `helm.parameters` or `helm.values`.

```yaml
  source:
    repoURL: https://charts.jetstack.io
    targetRevision: v1.21.2
    chart: cert-manager
    helm:
      parameters:
      - name: "crds.enabled"
        value: "true"
      values: |
        prometheus:
          enabled: false
```

### Tool support: OCI

Helm charts can also be pulled from OCI registries (e.g. Amazon ECR, Google GCR, Docker Hub).
As a Helm source, the registry goes in `repoURL` without the `oci://` scheme:

```yaml
  source:
    repoURL: registry-1.docker.io/bitnamicharts  # no oci:// prefix
    targetRevision: 15.9.0

From nq-rdl/agent-extensions, CC-BY-4.0.

More from nq-rdl/agent-extensions