blumeops/argocd/manifests/devpi/statefulset.yaml
Erich Blume 3ab67dd222 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>
2026-01-20 11:06:25 -08:00

64 lines
1.5 KiB
YAML

apiVersion: apps/v1
kind: StatefulSet
metadata:
name: devpi
namespace: devpi
spec:
serviceName: devpi
replicas: 1
selector:
matchLabels:
app: devpi
template:
metadata:
labels:
app: devpi
spec:
securityContext:
fsGroup: 1000
containers:
- name: devpi
# 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"
- "--host"
- "0.0.0.0"
- "--port"
- "3141"
- "--outside-url"
- "https://pypi.tail8d86e.ts.net"
ports:
- containerPort: 3141
name: http
volumeMounts:
- name: data
mountPath: /devpi
resources:
requests:
memory: "128Mi"
cpu: "100m"
limits:
memory: "512Mi"
cpu: "500m"
livenessProbe:
httpGet:
path: /+api
port: 3141
initialDelaySeconds: 30
periodSeconds: 30
readinessProbe:
httpGet:
path: /+api
port: 3141
initialDelaySeconds: 10
periodSeconds: 10
volumeClaimTemplates:
- metadata:
name: data
spec:
accessModes: ["ReadWriteOnce"]
resources:
requests:
storage: 50Gi