k8sgpt-ai/k8sgpt-operator

Automatic SRE Superpowers within your Kubernetes cluster

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

k8sgpt-ai/k8sgpt-operator has 450+ stars and 100+ forks on GitHub, is written in Go, and was last pushed on Oct 10, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 15th, 2026
Created on April 1st, 2023
Open Issues & Pull Requests: 32 (+0)
GitHub issues: Enabled
Number of forks: 146
Total Stargazers: 486 (+0)
Total Subscribers: 2 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.0 days
Mean response time: 100.3 days
90th percentile: 241.3 days
Tracked items: 86

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 613 days
Stale 30+ days: 9
Stale 90+ days: 7

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 2
Events in 7 days: 6

Top labels

  • bug (36)
  • Help Wanted (26)
  • feature (19)
  • dependencies (17)
  • Enhancement (9)
  • good first issue (8)
  • Good (2)
  • autorelease: tagged (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

The operator addresses the challenge of identifying and fixing Kubernetes failures by deploying K8sGPT as a managed workload within your cluster. It analyzes cluster state using an AI backend of your choice and generates actionable insights. The tool includes an alpha-stage auto-remediation feature that can repair certain workload failures, such as image pull errors, with built-in safety mechanisms: the LLM never receives write authority, the operator independently calculates JSON patches, validates changes against the Kubernetes API server in dry-run mode, and applies updates only to owning workloads rather than ephemeral pods.

The operator suits teams running Kubernetes who want centralized, AI-assisted diagnostics without manual intervention. It is particularly valuable for platform engineering scenarios where you manage multiple clusters, as it can monitor remote clusters by accepting kubeconfig values. The tool automatically rolls out updated credentials when AI provider secrets change, eliminating manual restarts. Auto-remediation is deliberately opt-in and currently alpha; you choose which AI provider to use and configure the remediation policy independently. The operator supports multiple AI backends through a pluggable provider model.

Development activity shows consistent engagement with the core functionality. The project maintains active issue triage and responds to user questions. Pull requests receive review and integration. The codebase receives updates addressing both feature additions and operational improvements. Documentation is kept current alongside feature releases, particularly around the auto-remediation safety model and provider configuration.