tnm

ArgoCD Load Testing Script

A bash script to create realistic ArgoCD applications for load testing and demo purposes.

Quick Start

# Download the script
curl -O https://gist.githubusercontent.com/tnm/f2cc981d822f86a2828ece6b39d359a4/raw/load-test-argocd.sh
chmod +x load-test-argocd.sh

tnm

#!/bin/bash
#
# ArgoCD Load Testing Script
#
# Creates realistic ArgoCD applications for load testing Cased CD Enterprise.
#
# USAGE:
#   ./load-test-argocd.sh [NUM_APPS]
#
# EXAMPLES:

tnm

Confirm IPv6 Binding Issue and Test Fix

The Problem

The backend is listening on IPv6 only (:::8081), but nginx is trying to connect via IPv4.

Confirmation Tests

1. Confirm IPv6-only binding

tnm

Debug Commands for Cased CD Enterprise 502 Error

Run these commands inside the pod to diagnose the 502 Bad Gateway issue.

Priority 1: Check Backend Status

# 1. Check if the backend process is running
ps aux | grep cased-backend

tnm

How to Set imagePullSecrets in ArgoCD Application

The Problem

You can't use --set imagePullSecrets[0].name=... in ArgoCD. Instead, you need to add it to the helm.values section of your ArgoCD Application.

---

Solution: Edit Your ArgoCD Application

tnm

Cased CD Enterprise - Install in Default Namespace (Josh Customer)

Good news!

Your secret is already in the default namespace, so let's install Cased CD there too!

kubectl get secret cased-cd-registry -n default
# NAME                TYPE                             DATA   AGE
# cased-cd-registry kubernetes.io/dockerconfigjson 1 16s

tnm

Cased CD Enterprise - Fix for Josh Customer

Problem: Secret in wrong namespace

Your secret is in default namespace but needs to be in argocd namespace!

# You have this (wrong):
kubectl get secret cased-cd-registry -n default

tnm

Cased CD Enterprise - Clean Install for Josh Customer

Step 1: Clean up existing installation

Remove any existing Cased CD installation:

# Uninstall Helm release if it exists
helm uninstall cased-cd -n argocd

tnm

Cased CD Enterprise Setup - Josh Customer

Your kubectl command is failing due to shell escaping issues. Use this YAML approach instead:

Step 1: Create registry-secret.yaml

Save this to a file called registry-secret.yaml:

apiVersion: v1

tnm

Comprehensive Debug - Josh

Run ALL of these and send back the output:

1. Check Frontend ARGOCD_SERVER Setting

kubectl get deployment cased-cd -n argocd -o yaml | grep -A2 "ARGOCD_SERVER"

2. Watch Logs During Login Attempt