Skip to content

Update argocd-ops login to SSO #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stephen-tatari merged 3 commits into from
Mar 5, 2026
Merged

Update argocd-ops login to SSO #34

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cb957f1
Update argocd-ops login to use SSO
stephen-tatari Mar 5, 2026
ad6c0aa
Remove --sso-port from troubleshooting
stephen-tatari Mar 5, 2026
88f4ef7
Optimize skill description for triggering
stephen-tatari Mar 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 9 additions & 18 deletions argocd-ops/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
name: argocd-ops
description: Manage ArgoCD applications via CLI - verify sync status, trigger jobs from cronjobs, refresh apps, and toggle auto-sync/self-heal settings. Use when deploying, debugging sync issues, or running manual jobs in ArgoCD-managed clusters.
description: Operate existing ArgoCD applications via the argocd CLI — check sync status, refresh or hard-refresh apps, look up Application names from ApplicationSets, toggle auto-sync and self-heal, and log into ArgoCD via SSO. Use this skill whenever the user mentions ArgoCD sync status, ArgoCD app refresh, ArgoCD login, disabling or enabling auto-sync or self-heal, looking up ArgoCD applications, or checking if a deploy has synced. This is for day-to-day ArgoCD operations, not for installing ArgoCD, writing ApplicationSet manifests, configuring RBAC, or setting up notifications.
model: claude-haiku-4-5-20251001
allowed-tools:
- Bash(argocd:*)
Expand Down Expand Up @@ -42,20 +42,14 @@ Ask the user for:

### Step 2: Login to ArgoCD

Determine the ArgoCD namespace and login:
Login via SSO:

```bash
# Determine namespace (ops uses argocd-infra, others use argocd)
if [ "<cluster>" = "ops" ]; then
ARGOCD_NS="argocd-infra"
else
ARGOCD_NS="argocd"
fi

# Login using subshell for password (no temp files)
argocd login argocd.<cluster>.tatari.dev --username admin \
--password "$(kubectl --context <cluster> get secret -n "$ARGOCD_NS" argocd-initial-admin-secret -o jsonpath='{.data.password}' | base64 -d)" \
--grpc-web
# Determine server
ARGOCD_SERVER="argocd.<cluster>.tatari.dev"

# Login via SSO
argocd login "$ARGOCD_SERVER" --sso --grpc-web
```

### Step 3: Perform Operations
Expand Down Expand Up @@ -163,11 +157,8 @@ kubectl --context <cluster> get job "$JOB_NAME" -n <namespace> \
# Verify cluster context exists
kubectl config get-contexts | grep <cluster>

# Check if secret exists
kubectl --context <cluster> get secret -n argocd argocd-initial-admin-secret

# For ops cluster, check argocd-infra namespace
kubectl --context ops get secret -n argocd-infra argocd-initial-admin-secret
# Ensure a browser is available for the SSO flow
# If running headless or over SSH, SSO login will not work
```

### App not found
Expand Down