Fix devpi image path for minikube registry access

- Use host.containers.internal:5050 instead of registry.tail8d86e.ts.net
- Minikube's CRI-O can't resolve Tailscale DNS, but can reach Zot via podman host
- Also update CLAUDE.md to spell out kubectl commands (fish abbreviations don't work in scripts)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CLAUDE.md

@@ -88,14 +88,16 @@ Most services are migrating to Kubernetes. These are managed via ArgoCD using th
 
 **Useful commands:**
 ```fish
-argocd app list                    # List all apps
-argocd app get <app>               # Get app details
-argocd app diff <app>              # Preview changes before sync
-argocd app sync <app>              # Sync an app
-ki get pods -n <namespace>         # Check pods (ki = kubectl --context=minikube-indri)
-k9i                                # k9s for the minikube-indri context
+argocd app list                                        # List all apps
+argocd app get <app>                                   # Get app details
+argocd app diff <app>                                  # Preview changes before sync
+argocd app sync <app>                                  # Sync an app
+kubectl --context=minikube-indri get pods -n <namespace>  # Check pods
+kubectl --context=minikube-indri logs -n <namespace> <pod>  # View logs
 ```
 
+Note: The user has fish abbreviations `ki` for `kubectl --context=minikube-indri` and `k9i` for `k9s --context=minikube-indri`, but these only work in interactive shells.
+
 ### Indri Services (via Ansible)
 
 Some services remain on indri outside of Kubernetes:

argocd/manifests/devpi/statefulset.yaml

@@ -18,7 +18,8 @@ spec:
         fsGroup: 1000
       containers:
         - name: devpi
-          image: registry.tail8d86e.ts.net/blumeops/devpi:latest
+          # Use host.containers.internal for minikube's CRI-O to reach Zot on indri
+          image: host.containers.internal:5050/blumeops/devpi:latest
           args:
             - "--serverdir"
             - "/devpi"