<p>Kubernetes has become the foundation of modern cloud-native infrastructure, yet its operational complexity remains a persistent barrier. Administrators must navigate a vast API surface, manage heterogeneous workloads, and coordinate tasks across disconnected tools—often requiring precise commands, declarative configuration files, and deep domain expertise. This paper presents <b>KubeIntellect</b>, a Large Language Model (LLM)-powered system for end-to-end Kubernetes management through natural language. KubeIntellect spans all major categories of Kubernetes operations—read, write, delete, exec, access control, and lifecycle management—through a supervisor-coordinated set of domain-specialized agents, with human-in-the-loop (HITL) confirmation on all mutating operations. Operations outside the static tool set are handled by the Code Generator Agent, which synthesizes, validates, and registers new Kubernetes tools at runtime. The Code Generator Agent executes synthesized tools in an in-process Python REPL rather than a separate process or container; process-level isolation between synthesized code and the host runtime is&#xa0;therefore not enforced, and a defense-in-depth model comprising static analysis, API-call validation, and mandatory human-in-the-loop review constitutes the primary mitigation. Migration to pod-level isolation is a planned hardening step. Evaluation on a live four-node Kubernetes cluster (170 pods across 18 namespaces) shows: a <b>75% pass rate</b> (12/16; 95% CI: 51%–91%; mean rubric score 31.2/40) on a 16-scenario controlled fault-injection corpus scored on an 8-dimension LLM-judge rubric; a <b>+25 percentage-point improvement</b> over a tool-less GPT-4o baseline on the same scenarios (75% vs. 50%); a <b>93% query resolution rate</b> (186/200) with an <b>81.8% synthesis success rate</b> (63/77 novel tool requests) on a 200-query operational corpus; and end-to-end latency in the <b>7–10&#xa0;s</b> range at a mean API cost of <b>$0.036/query</b> for read-only workloads and <b>$0.039/query</b> overall. A reproducible demo environment is available on a public managed-Kubernetes service, with a local single-node option for readers without cloud access. These results demonstrate that domain-specific multi-agent orchestration, structured HITL confirmation, and runtime tool synthesis together yield substantially higher task completion than general-purpose LLM reasoning on Kubernetes operations.</p>

错误:搜索内容不能为空,请输入英文关键词
错误:关键词超出字数限制,请精简
高级检索

KubeIntellect: A Modular LLM-Orchestrated Agent Framework for End-to-End Kubernetes Management

  • Mohsen Seyedkazemi Ardebili,
  • Andrea Bartolini

摘要

Kubernetes has become the foundation of modern cloud-native infrastructure, yet its operational complexity remains a persistent barrier. Administrators must navigate a vast API surface, manage heterogeneous workloads, and coordinate tasks across disconnected tools—often requiring precise commands, declarative configuration files, and deep domain expertise. This paper presents KubeIntellect, a Large Language Model (LLM)-powered system for end-to-end Kubernetes management through natural language. KubeIntellect spans all major categories of Kubernetes operations—read, write, delete, exec, access control, and lifecycle management—through a supervisor-coordinated set of domain-specialized agents, with human-in-the-loop (HITL) confirmation on all mutating operations. Operations outside the static tool set are handled by the Code Generator Agent, which synthesizes, validates, and registers new Kubernetes tools at runtime. The Code Generator Agent executes synthesized tools in an in-process Python REPL rather than a separate process or container; process-level isolation between synthesized code and the host runtime is therefore not enforced, and a defense-in-depth model comprising static analysis, API-call validation, and mandatory human-in-the-loop review constitutes the primary mitigation. Migration to pod-level isolation is a planned hardening step. Evaluation on a live four-node Kubernetes cluster (170 pods across 18 namespaces) shows: a 75% pass rate (12/16; 95% CI: 51%–91%; mean rubric score 31.2/40) on a 16-scenario controlled fault-injection corpus scored on an 8-dimension LLM-judge rubric; a +25 percentage-point improvement over a tool-less GPT-4o baseline on the same scenarios (75% vs. 50%); a 93% query resolution rate (186/200) with an 81.8% synthesis success rate (63/77 novel tool requests) on a 200-query operational corpus; and end-to-end latency in the 7–10 s range at a mean API cost of $0.036/query for read-only workloads and $0.039/query overall. A reproducible demo environment is available on a public managed-Kubernetes service, with a local single-node option for readers without cloud access. These results demonstrate that domain-specific multi-agent orchestration, structured HITL confirmation, and runtime tool synthesis together yield substantially higher task completion than general-purpose LLM reasoning on Kubernetes operations.