<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Agents in Kubernetes Without Laptop Credentials (feat. KAOP)</title><link>https://devopstoolkit.live/devops/ai-agents-in-kubernetes-without-laptop-credentials-feat-kaop/index.html</link><description>Why would anyone put a platform between an AI agent and a Kubernetes cluster? Claude Code can fix clusters on its own. It finds the cause, rules out the red herrings, changes only what it should, and verifies the fix. No platform, no special setup. Just a terminal, a prompt, and my credentials. That works for one person. Does it work for a company, where it means every laptop holding the keys to production, nobody else approving what the agents change, no shared record of what they did or what it cost, and nothing happening unless someone sits at a keyboard?
To find out, I tried a platform built for exactly that: Komodor’s Agentic Operations Platform, KAOP for short. It lets you define agents and run them inside your clusters instead of on someone’s laptop, as services with their own identities. It sends their risky actions to people for approval, and it keeps a record of what they did and what it cost. It does more than that, like a catalog of ready-made agents, guardrails on the tools agents call, and side-by-side testing of a new model or prompt against the current one, and I’ll come back to those at the end.
So, do we need a platform at all? What changes when there is one? And is KAOP the one to pick? To answer that, we’ll fix the same incident four times: with Claude Code alone, with Claude Code going through KAOP, and twice with nobody at a laptop. One of those fixes goes wrong in a way that says something about agents in general, not only about KAOP.</description><generator>Hugo</generator><language>en-us</language><lastBuildDate/><atom:link href="https://devopstoolkit.live/devops/ai-agents-in-kubernetes-without-laptop-credentials-feat-kaop/index.xml" rel="self" type="application/rss+xml"/></channel></rss>