Quick Fix for TLS Error - Cased CD Enterprise

josh-quick-fix.md

Quick Fix for TLS Error - Josh

The issue is that the enterprise backend is trying to connect to ArgoCD over HTTPS with a self-signed cert.

Quick Fix (Patch the Running Deployment)

# Update the enterprise deployment to use HTTP instead of HTTPS
kubectl set env deployment/cased-cd-enterprise \
  ARGOCD_SERVER=http://argocd-server.argocd.svc.cluster.local \
  -n default

# Wait for the pod to restart
kubectl rollout status deployment/cased-cd-enterprise -n default --timeout=60s

# Check the logs - should see successful connections now
kubectl logs -n default deployment/cased-cd-enterprise --tail=20

After this, try logging in again. The 502 errors should be gone.

---

Note: Your pods are in the default namespace, not argocd namespace, because the manifest has hardcoded namespace: default.