Migrate devpi from minikube to indri (launchd) #341
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "migrate-devpi-to-indri"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Devpi was crash-looping under memory pressure on the minikube StatefulSet, breaking the Python toolchain across the repo (
mise run docs-mikado,prek, everyuv pip install). It moves to indri as a native LaunchAgent.What changed
ansible/roles/devpi/: installsdevpi-server+devpi-webinto a uv-managed venv, initializes the server-dir on first run via 1Password root password, runs as a LaunchAgent (mcquack.eblume.devpi) bound to127.0.0.1:3141. Bootstraps from upstream PyPI (so devpi can install itself on a fresh box).pypi.ops.eblu.menow proxies tohttp://localhost:3141.indri.ymlgains pre_tasks for the root password and the new role.type: argocdtotype: ansible.apps/devpi.yamlandmanifests/devpi/. The in-cluster Application, namespace, and PVC have been deleted.docs/how-to/operations/devpi-on-indri.md;restart-indri.mdlists devpi in the LaunchAgent stop list.Already deployed (live on indri)
launchctl list mcquack.eblume.devpi→ PID 53888curl https://pypi.ops.eblu.me/+apireturns 200 ✅mise run docs-mikadoworks again ✅~erichblume/devpi/server-dir/Test plan
mise run services-check(after merge)pypi.ops.eblu.me(prek, uv-script tasks, dagger pipelines)Context
This is the C1 prelude to a planned C2 chain (
mikado/retire-minikube-indri) to retire minikube on indri entirely. Doing devpi as a standalone C1 was the right call because (a) it was urgent — it was breaking the toolchain — and (b) it shakes out the migration recipe before we commit to a multi-leaf chain.