{"slug":"claude-code-propose-a-cluster-change-and-wait","title":"Propose a cluster change through Lumovi and wait for me","summary":"Claude Code handles this as a draft: Ask for a Kubernetes change through Lumovi's MCP server. The change is checked, shown as a diff with the kubectl that would do it, and waits. I approve or reject.","agent":"Claude Code","agentSlug":"claude-code","category":"Operations","categorySlug":"operations","roles":["Software engineer"],"roleSlugs":["software-engineer"],"industries":["Software"],"industrySlugs":["software"],"jobs":["workflow-automation"],"topic":"Work & Ops","topicSlug":"work-and-ops","score":18,"difficulty":"hard","estCost":"Lumovi is described as free and open source. Claude Code is the plan you already use. The cluster is one you already administer.","costTier":"low","timeSaved":"Drafting the change and the matching kubectl. An estimate, not a measurement.","prompt":"You may inspect the cluster only through the Lumovi MCP server, and only in the namespaces I named.\n\nIf you want a change, propose it. Include why, the diff, and the kubectl command that does the same thing. Then wait.\n\nDo not apply a change. Do not scale, delete, restart, or roll back unless I approve that exact proposal. If I reject it or the wait expires, stop. Do not retry a rejected change with different wording.","steps":[{"title":"Point an MCP client at Lumovi","detail":"The Lumovi page says any MCP client can work through it, on the desktop app or a team's server, as you. This playbook uses Claude Code. Limit what it may do, down to the namespace."},{"title":"Ask for one change and read the approval card","detail":"The page's example is a proposal to scale a deployment. The card shows the reason, the diff, and the equivalent kubectl. The cluster checks the change, then it waits."},{"title":"Approve or reject yourself","detail":"You approve that card or you reject it. A note can send the assistant back, as in the page's example of refusing a scale during a sale. Nothing applies before that."}],"sourceUrl":"https://lumovi.dev/","sourceNote":"Lumovi homepage. It returned HTTP 200 on 17 Oct 2026. The AI assistants section says Lumovi is an MCP server, you choose what an agent may do down to the namespace, and a change waits with the diff, the reason, and the kubectl. The Hacker News post the same day is https://news.ycombinator.com/item?id=50128693. The page says any MCP client works; Claude Code is the client named in this playbook. Prompt and stop rules are an AI Playbook Gems adaptation, not a vendor quote; unverified.","date":"2026-10-17","verified":false,"status":"unverified","sponsorUrl":"","metrics":[{"label":"Hands-on time","value":"Reading the diff and the kubectl before approving"},{"label":"You still approve","value":"Every change to the cluster"}],"faq":[{"question":"Has this Claude Code playbook been re-run for the catalog?","answer":"No. Status is unverified. The Lumovi page and the Hacker News post were checked on 17 Oct 2026. The prompt is an adaptation."},{"question":"What stays human?","answer":"Approval. The page shows the change waiting until a person approves or rejects it."}],"url":"https://aiplaybookgems.com/usecases/claude-code-propose-a-cluster-change-and-wait","jsonUrl":"https://aiplaybookgems.com/api/usecases/claude-code-propose-a-cluster-change-and-wait"}