What k8sgpt-ai/k8sgpt shipped
Written by FoxPlug from the repository's own releases; not affiliated with K8sgpt. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/k8sgpt-ai/k8sgpt; K8sgpt did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of October 5, 2026
What shipped
- Released version 0.4.40, adding a ResourceClaim analyzer for missing DeviceClasses and fixing several analyzer issues. Release
- NetworkPolicy analysis now honors matchExpressions in pod selectors, instead of only reading matchLabels. Pull request #1818
- The PodDisruptionBudget analyzer now reports blocked PDBs whose selector is empty or uses matchExpressions. Pull request #1797
- PDB selector operators are now rendered as readable phrases such as NotIn and DoesNotExist. Pull request #1820
- The OLM analyzers no longer panic on catalogs that have no image. Pull request #1815
- The StatefulSet analyzer now honors start ordinals other than zero. Pull request #1759
- The Kyverno policy-report scheme is now registered once in NewClient, avoiding concurrent map writes. Pull request #1777
- API doc lookups for the MutatingWebhookConfiguration and ValidatingWebhookConfiguration analyzers are now correct. Pull request #1802
Why it matters
This week fixes analyzers that could report the wrong result or fail silently. NetworkPolicy and PodDisruptionBudget selectors are now read fully, StatefulSet and OLM analysis no longer stops early or panics, webhook doc lookups are right, and version 0.4.40 ships these changes along with the new ResourceClaim check.
Changelog entry
- Add ResourceClaim analyzer for missing DeviceClasses Release
- Close the custom analyzer gRPC connection after each analysis Release
- Correct API doc lookups for the webhook analyzers Release
- Honor matchExpressions in NetworkPolicy pod selectors Pull request #1818
- Report blocked PDBs whose selector is empty or uses matchExpressions Pull request #1797
- Render PDB selector operators as readable phrases Pull request #1820
- Stop the OLM analyzers panicking on catalogs without an image Pull request #1815
- Honor StatefulSet start ordinals Pull request #1759
- Register kyverno policy-report scheme once to avoid concurrent map writes Pull request #1777
K8sgpt v0.4.40 is out. This week: NetworkPolicy matchExpressions and PDB selectors are honored, OLM no longer panics, StatefulSet start ordinals work, and webhook doc lookups are fixed.
K8sgpt v0.4.40 is out. This week we fixed several analyzers that could produce wrong or missing results: NetworkPolicy selectors now honor matchExpressions, the PodDisruptionBudget analyzer reports blocked PDBs with empty or matchExpressions selectors, and selector operators read as plain phrases like NotIn and DoesNotExist. The OLM analyzers no longer panic on catalogs without an image, the StatefulSet analyzer honors start ordinals, the Kyverno scheme is registered once in the client, and the webhook analyzers now resolve API docs correctly. The release also adds a ResourceClaim analyzer for missing DeviceClasses.
Week of September 28, 2026
What shipped
- Fixed gRPC connection leaks where custom analyzers left one connection open per analysis call. Pull request #1800
- Fixed ConfigMap tracking in cluster-wide analysis to properly scope ConfigMaps to their namespaces. Pull request #1812
- Fixed Deployment, DaemonSet, and Webhook analyzers to use caller-supplied context instead of context.Background(). Pull request #1732
- Fixed GatewayClass analyzer to properly locate the Accepted condition in unordered status condition slices. Pull request #1806
- Fixed Ingress analyzer to detect missing default backend services specified at the top level. Pull request #1810
- Fixed Job analyzer to detect failed jobs that exceed activeDeadlineSeconds and report DeadlineExceeded/JobFailed conditions. Pull request #1809
- Fixed PersistentVolumeClaim analyzer to report FailedBinding events when claims remain pending. Pull request #1808
- Fixed S3 cache backend to paginate through all ListObjectsV2 results instead of stopping after the first response. Pull request #1811
- Added recognition of EKS node monitoring agent conditions (KernelReady, NetworkingReady, StorageReady, ContainerRuntimeReady, AcceleratedHardwareReady). Pull request #1798
- Fixed serve command to respect K8SGPT_BACKEND environment variable on every restart, not just initial startup. Pull request #1749
Why it matters
This week addresses resource leaks in custom analyzers and fixes detection accuracy across multiple analyzer types. Improvements to context handling, condition checking, and status reporting make the project more reliable in cluster environments and reduce false negatives in failure detection.
Changelog entry
- Close gRPC connections from custom analyzers after each analysis to prevent connection leaks Pull request #1800
- Scope ConfigMap usage tracking to pod namespace in cluster-wide analysis Pull request #1812
- Use caller-supplied context in Deployment, DaemonSet, and Webhook analyzers Pull request #1732
- Use apimeta.FindStatusCondition to locate GatewayClass Accepted condition Pull request #1806
- Recognize EKS node monitoring agent conditions (KernelReady, NetworkingReady, StorageReady, ContainerRuntimeReady, AcceleratedHardwareReady) Pull request #1798
- Report missing default backend services in Ingress analyzer Pull request #1810
- Use apimeta.FindStatusCondition to locate PDB DisruptionAllowed condition Pull request #1807
- Report DeadlineExceeded and JobFailed conditions in Job analyzer Pull request #1809
- Report FailedBinding events in PersistentVolumeClaim analyzer Pull request #1808
- Paginate S3 object listings to consume all ListObjectsV2 pages Pull request #1811
- Honour K8SGPT_BACKEND environment variable on every serve start Pull request #1749
- Handle empty AI responses and respect configured language setting Pull request #1756
This week's releases fix gRPC leaks in custom analyzers, improve Ingress and Job failure detection, and add EKS node condition support. Cluster-wide analysis and S3 caching are also more reliable.
K8sgpt improvements this week target reliability and detection accuracy: gRPC connection leaks in custom analyzers are fixed, GatewayClass and PDB analyzers now correctly find status conditions in unordered slices, Jobs that exceed deadline are detected, Ingress defaultBackend is validated, and PersistentVolumeClaim binding failures are reported. EKS node monitoring conditions are now recognized. Context handling and S3 pagination are fixed.
Week of September 21, 2026
What shipped
- Added ResourceClaim analyzer to check Kubernetes Dynamic Resource Allocation DeviceClass references and report missing device class names. Pull request #1768
- Fixed Deployment analyzer to skip replica mismatch reports during healthy rollouts when the controller has not yet observed the latest spec. Pull request #1743
- Fixed NetworkPolicy analyzer to scope pod lookups to the policy's namespace instead of searching cluster-wide. Pull request #1747
- Fixed analyzer to stop reporting local StorageClasses without provisioners as deprecated. Pull request #1779
- Updated release pipeline to use release tags for gating GoReleaser and container publishing instead of relying on release-please output. Pull request #1803
- Updated CONTRIBUTING.md to point to CNCF Slack instead of the expired invite link. Pull request #1799
Why it matters
This week addresses correctness in multiple analyzers that were generating false positives during normal cluster operations. The Deployment and NetworkPolicy fixes reduce noise for users dealing with rollouts and network policies, while the new ResourceClaim analyzer expands coverage for Kubernetes features. Release pipeline improvements ensure more reliable artifact publishing.
Changelog entry
- Feat: add ResourceClaim analyzer for missing DeviceClasses Pull request #1768
- Fix: ignore in-progress Deployment replica mismatches Pull request #1743
- Fix: scope NetworkPolicy pod lookup to policy namespace Pull request #1747
- Fix: stop reporting local StorageClasses as deprecated Pull request #1779
- Ci: run release jobs from the release tag Pull request #1803
- Docs: point CONTRIBUTING.md at CNCF Slack Pull request #1799
K8sgpt fixes false positives in Deployment and NetworkPolicy analysis, adds ResourceClaim analyzer for Dynamic Resource Allocation, and improves release reliability.
This week's K8sgpt updates focus on reducing false positives in cluster diagnostics. The Deployment analyzer now skips replica mismatches during healthy rollouts, and NetworkPolicy analysis correctly scopes pod lookups to policy namespaces. New support for ResourceClaim analyzer enables checking Kubernetes Dynamic Resource Allocation DeviceClass references. Release pipeline improvements ensure reliable artifact publishing.
Week of September 14, 2026
What shipped
- Released v0.4.39 with a new --resource flag to analyze single resources and a ValidatingAdmissionPolicy analyzer for Kubernetes admission policies. Release
- Added ValidatingAdmissionPolicy analyzer that reports CEL type-check warnings and validates policy bindings. Pull request #1765
- Fixed MCP list-events tool to send involvedObject filters as field selectors instead of filtering results locally. Pull request #1792
- Fixed analyzer event fetching to match full object identity including kind and UID, not just name. Pull request #1790
- Fixed service event scoping to respect endpoint namespaces. Pull request #1795
- Fixed service analyzer to filter events by involved object kind, preventing misattribution of events from other resources with the same name. Pull request #1783
- Fixed Security analyzer to resolve ClusterRole references in RoleBindings by checking roleRef.kind. Pull request #1755
- Fixed --anonymize flag to mask resource names appearing in Kubernetes event messages. Pull request #1778
- Fixed ReplicaSet analyzer to report ReplicaFailure conditions regardless of replica count. Pull request #1750
- Added safety check in OpenAIClient to handle empty completion choices from compatible backends. Pull request #1781
Why it matters
This week focused on event filtering accuracy and namespace isolation. Several fixes prevent events and resource references from being misattributed to the wrong objects, which directly improves diagnostic accuracy.
Changelog entry
- Add --resource flag to analyze a single resource Release
- Add ValidatingAdmissionPolicy analyzer Release
- Anonymise resource names in event-derived failures Pull request #1778
- Send involvedObject filters as a field selector in MCP list-events Pull request #1792
- Scope analyzer events to object identity Pull request #1790
- Scope service events to endpoint namespace Pull request #1795
- Filter service events by involved object kind Pull request #1783
- Resolve ClusterRole references in RoleBindings Pull request #1755
- Report ReplicaFailure regardless of replica count Pull request #1750
- Do not also report an unsupported scaleTargetRef as missing Pull request #1729
V0.4.39 shipped: new --resource flag for single-resource analysis, ValidatingAdmissionPolicy analyzer, and fixes for event scoping and object reference resolution.
V0.4.39 is out with improvements to event scoping and object reference handling. The new --resource flag lets you analyze individual resources, while the ValidatingAdmissionPolicy analyzer adds support for Kubernetes admission policies. This release includes multiple fixes to prevent event misattribution and improve namespace isolation in diagnostics.