Template devcontainer with Minikube for safely running an agent’s commands in isolation. React frontend + FastAPI backend are exposed via NodePort for easy local access; everything lives inside the devcontainer and local Minikube so the agent cannot affect your host.
- Devcontainer with Minikube, kubectl, Helm, Docker, Node 20, Python 3.13
- React frontend (NodePort 30081) and FastAPI backend (NodePort 30080)
- Local port-forward helper (
make forward) to reach the app at localhost:3000 (frontend) and localhost:8000 (backend) - Images are built locally and loaded into Minikube; no external registry required
- The agent runs entirely inside the devcontainer; Minikube is inside Docker-in-Docker, so scope is limited
- No host file edits or external ingress needed; access uses Minikube IP + NodePorts
- Make targets are constrained to cluster lifecycle, image build/load, and port forwarding
- Start/verify the cluster:
make setup - Build, load, deploy:
make deploy - Get access info:
make expose(orminikube ip -p devcontainer) - Optional: port-forward to localhost:
make forward(frontend 3000, backend 8000)
Access via Minikube IP:
- Frontend:
http://<MINIKUBE_IP>:30081 - Backend:
http://<MINIKUBE_IP>:30080
- The agent should run
make(defaulthelp) to see allowed commands. - Typical flow for the agent:
make setupmake deploymake exposeto learn IP/ports, ormake forwardif localhost access is needed
- Backend endpoints the agent can call:
- Health:
http://<MINIKUBE_IP>:30080/healthz - Quote:
http://<MINIKUBE_IP>:30080/quote
- Health:
- In-cluster addressing for agent code or jobs:
http://backendandhttp://frontend.
make/make help— list available targetsmake setup— ensure Minikube is upmake deploy— build, load, apply manifestsmake forward— port-forward to localhost (frontend 3000, backend 8000)make expose— print NodePort URLs with Minikube IPmake undeploy— delete k8s resourcesmake setup-clean— delete the Minikube cluster