Hysen Labskubernaut
An AIOps platform that closes the loop from Kubernetes alert to automated remediation: An AI Agent investigates via MCP tools, selects a fix from a pre-seeded workflow catalog and delegates execution (K8s Job, Tekton, Ansible) — or escalates with a full RCA. Approval gates, OPA policies, and audit trails keep humans in control.
Kubernaut
An AIOps platform that closes the loop from a Kubernetes alert to automated remediation using an LLM agent that investigates via MCP tools and executes fixes or escalates with an RCA.
How it operates
Kubernaut is an AIOps platform for intelligent Kubernetes remediation. It works in two modes: autonomous, where it detects signals, investigates root causes, and executes fixes end to end without human involvement, and interactive, where operators join an in progress investigation through MCP or A2A, guide the agent, and approve remediations in real time. The LLM powered agent uses native Go client-go bindings against the Kubernetes API, Prometheus and log endpoints to investigate, select a remediation workflow, and execute the fix, or escalate to a human with a full root cause analysis when it cannot resolve the issue. Full documentation covers architecture, installation and usage.
Safety controls
The README stresses that approval gates, Open Policy Agent policies and audit trails keep humans in control. The agent selects a fix from a pre seeded workflow catalog and delegates execution to a Kubernetes Job, Tekton, or Ansible, or escalates with a complete RCA. This is positioned as a step beyond rule based remediation, which the author compares to a thermostat that only handles known deterministic problems, whereas Kubernaut is described as a diagnostician that also adjusts the thermostat when the same symptom has multiple root causes. The interactive mode is the path for operators who want to stay in the loop.
Coverage and validation
The platform is validated against thirty seven runnable demo scenarios in a separate demo scenarios repository, covering real world Kubernetes failure modes across workload failures such as crash loops and stuck rollouts, resource and capacity issues such as maxed out horizontal pod autoscalers and persistent volume claim exhaustion, and infrastructure faults such as node failures and scheduling taints. The README embeds a non interactive autonomous demo of a CrashLoopBackOff scenario. The project is Apache-2.0 licensed, targets Kubernetes v1.32 or newer, and carries OpenSSF Scorecard and Best Practices badges.
Editorial conclusion
Kubernaut is Apache-2.0 licensed and reported twenty seven stars at indexing, with OpenSSF Scorecard and Best Practices badges shown in the README.
Community notes