V2 deployment qualification: signed images, staging rollout and live rollback
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, or code entry points. Start by mapping the deployment qualification flow and its Kubernetes admission, rollout, rollback, identity, NetworkPolicy, and MetaHarness components. Done means a staging workload passes admission, rejects unauthorized effects, survives a failed rollout, restores the prior revision, and emits independent provenance evidence.
Written by the indexing model from the issue text.
Description
The v2 revival supplies deterministic local artifact generation, policy validation, previews, artifact rollback, official SDK MCP/CLI, MetaHarness profiles and Autogenous evidence gates. Historical model-selected shell execution is retired.
Production qualification remains explicit:
- Supply real reviewed image/base digests and compatible app/server executable.
- Verify image signatures and vulnerabilities with deployment-owned trust roots.
- Exercise Kubernetes server-side dry run and actual rollout under a namespace-scoped short-lived identity.
- Validate NetworkPolicy with the deployed CNI and readiness/liveness behavior.
- Test live revision compare-and-swap plus rollback and any database restoration separately.
- Configure durable MetaHarness field-memory storage and identity verifier; do not treat scaffold as deployed service.
Acceptance: staging workload passes admission, rejects unauthorized effects, survives a failed rollout, restores the prior revision and emits independent provenance evidence. No cloud credentials were accessed or production changes executed by the revival.
- Dominant language
- Python
- Stars
- 55
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ruvnet/agentic-devops
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ruvnet/agentic-devops#6 ·
All issues in ruvnet/agentic-devops
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
AstrBotDevs/AstrBot#10720 ·
Maintainers usually reply within 1 day
-
fix(xiaomi): curated picker list still offers six ids that return 400 (plan-limited vs retired)Opencause/upstream comp/cli P2 provider/other tool/file type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#143900 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
WLAN-Pi/wlanpi-profiler#341 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day