Cased CD Enterprise - CORRECT Production Credentials for Josh

josh-correct-production-credentials.md

Cased CD Enterprise - CORRECT Production Credentials (Josh)

The Problem

You were using credentials from the LOCAL dev database. Here are your REAL production credentials:

• Username: joshpeek
• Token: nyH07X8C4iCKuRWt5TECgnTdKUgr2iVDY445P_zayhg
• Email: [email protected]

---

Step 1: Test the registry (should work now!)

curl -u "joshpeek:nyH07X8C4iCKuRWt5TECgnTdKUgr2iVDY445P_zayhg" https://registry.cased.com/v2/

You should see: {} (HTTP 200 OK)

---

Step 2: Clean up old installation

# Delete old stuff
helm uninstall cased-cd -n default 2>/dev/null
kubectl delete secret cased-cd-registry -n default 2>/dev/null
sleep 10

---

Step 3: Create the secret with CORRECT credentials

cat > registry-secret.yaml << 'YAML'
apiVersion: v1
kind: Secret
metadata:
  name: cased-cd-registry
  namespace: default
type: kubernetes.io/dockerconfigjson
data:
  .dockerconfigjson: eyJhdXRocyI6IHsicmVnaXN0cnkuY2FzZWQuY29tIjogeyJ1c2VybmFtZSI6ICJqb3NocGVlayIsICJwYXNzd29yZCI6ICJueUgwN1g4QzRpQ0t1Uld0NVRFQ2duVGRLVWdyMmlWRFk0NDVQX3pheWhnIiwgImF1dGgiOiAiYW05emFIQmxaV3M2Ym5sSU1EZFlPRU0wYVVOTGRWSlhkRFZVUlVObmJsUmtTMVZuY2pKcFZrUlpORFExVUY5NllYbG9adz09In19fQ==
YAML

kubectl apply -f registry-secret.yaml

---

Step 4: Verify the secret

# Check secret exists
kubectl get secret cased-cd-registry -n default

# Verify contents
kubectl get secret cased-cd-registry -n default -o jsonpath='{.data.\.dockerconfigjson}' | base64 -d

You should see:

{
  "auths": {
    "registry.cased.com": {
      "username": "joshpeek",
      "password": "nyH07X8C4iCKuRWt5TECgnTdKUgr2iVDY445P_zayhg",
      "auth": "am9zaHBlZWs6bnlIMDdYOEM0aUNLdVJXdDVURUNnblRkS1VncjJpVkRZNDQ1UF96YXloZw=="
    }
  }
}

---

Step 5: Install Cased CD Enterprise

helm repo add cased https://cased.github.io/cased-cd
helm repo update

helm install cased-cd cased/cased-cd \
  --namespace default \
  --set enterprise.enabled=true \
  --set enterprise.auditTrail.enabled=true \
  --set enterprise.image.repository=registry.cased.com/cased/cased-cd-enterprise \
  --set imagePullSecrets[0].name=cased-cd-registry

---

Step 6: Watch pods come up

kubectl get pods -n default -w

Wait for cased-cd-enterprise-* pods to show Running and 1/1 ready. Press Ctrl+C when done.

---

Step 7: Access the UI

kubectl port-forward svc/cased-cd 8080:80 -n default

Then visit: http://localhost:8080

---

kubectl command alternative (if you prefer)

kubectl create secret docker-registry cased-cd-registry --docker-server=registry.cased.com --docker-username=joshpeek --docker-password=nyH07X8C4iCKuRWt5TECgnTdKUgr2iVDY445P_zayhg -n default

(But the YAML method is more reliable!)

---

Summary

The issue: You were using local dev credentials (Josh Customer / g8Nlw7kMhKTTTlbL...)

The fix: Use production credentials (joshpeek / nyH07X8C4iCKuRWt5TEC...)

Now the registry should accept your credentials and Kubernetes can pull the image!

Support: [email protected]