JUMI

Policy-agnostic in-cluster execution data-plane app for Kubernetes, built on a Kubernetes native baseline and integrated with Kueue without making core execution semantics depend on it.

Commands

• make test: run the root-module unit test suite
• make test-regression: rerun the AH seam, executor, metrics, and observe regression packages
• make coverage: generate reports/cover.out and reports/coverage.txt
• make lint: fail gate for root-module code
• make lint-security: report-only gosec observation
• make vuln: report-only govulncheck observation
• make vuln-all: report-only govulncheck over all packages
• make preflight-publish-local: check Harbor reachability from the current host
• make preflight-publish-remote: check Harbor reachability from 100.123.80.48
• make preflight-ko-remote: verify remote ko, Harbor TLS trust, and Docker auth on 100.123.80.48
• make runtime-build-local: local runtime image build for CLI validation only
• make runtime-check-local: local nan CLI contract check against the local image
• make runtime-align-check: compare the JUMI Containerfile runtime pin with the local node-artifact-runtime checkout
• make runtime-smoke-remote: remote K8s smoke entrypoint
• make ko-publish-remote: build and deploy the JUMI service image with ko on 100.123.80.48
• make ko-smoke-remote: run the live smoke after a ko service image publish

Notes:

• GOLANGCI_LINT=/path/to/golangci-lint make lint can be used to reuse an existing local binary instead of bootstrapping ./bin/golangci-lint.
• make lint-security is intentionally observation-only; current findings should be triaged separately from the fail gate.
• Local build is not publish authority. Runtime image publish and K8s smoke authority live on 100.123.80.48.
• Remote ko publish requires Harbor TLS trust in the remote OS trust store and Harbor auth in ~/.docker/config.json.
• GitHub is the source of truth. Harbor is the primary runtime registry. GHCR is the backup registry.
• When SYNC_BACKUP_REGISTRY=true, Harbor and GHCR publish must both succeed for the same source commit.

Documents

• JUMI Final Development Goal
• JUMI Design
• JUMI State Transition Spec
• JUMI Cancel / Failure / Retry Semantics
• JUMI gRPC Contract Draft
• JUMI Executable Run Spec Draft
• JUMI Sprint Plan
• JUMI Scheduler Boundary
• JUMI Node Runtime Artifact Contract
• JUMI nan PID 1 Shutdown Integration Plan
• JUMI ko Service Image Migration Plan
• JUMI Node Runtime Base Image Plan
• JUMI Artifact Helper Repo Split Plan
• JUMI AH nan Integration Review
• JUMI Remote Fetch v0 Sprint Plan
• JUMI simple_http Artifact Source v0 Plan
• Sprint 3B Design: Pure K8s Node-local Handoff Happy Path
• Artifact Source Registry / Materialization Source Layer
• Sprint 3C-3 Security / Integrity Guardrails
• JUMI Durable Registry Options
• JUMI Implementation Status 2026-05-14
• JUMI Layered Error Guidelines Review
• JUMI dag-go Integration Contract Review
• JUMI dag-go Migration Checklist
• JUMI spawner Integration Contract Review
• JUMI Locality Semantics Review
• JUMI Execution Environment Boundary
• JUMI Registry Sync Policy