AI Assistant for Calico: Troubleshooting at the Speed of Thought

Beyond Manual Log Analysis Natural Language Insights Proactive Security and Policy Optimization Real-World Scenario: Rapidly Resolving a Blocked Service Connection A New Standard for Platform Operations Experience the Power of AI Assistant for Calico Despite the wealth of data available, distilling a coherent narrative from a Kubernetes cluster remains a challenge for modern infrastructure teams. Even with powerful visualization tools like the Policy Board, Service Graph, and specialized dashboards, users often find themselves spending significant time piecing together context across different screens. Making good use of this data to secure a cluster or troubleshoot an issue becomes nearly impossible when it requires manually searching across multiple sources to find a single “connecting thread. ” Inevitably, security holes happen, configurations conflict causing outages, and teams scramble to find that needle-in-the-haystack cause of cluster instability. A new approach is needed to understand the complex layers of security and the interconnected relationships among numerous microservices. Observability tools need to not only organize and present data in a coherent manner but proactively help to filter and interpret it, cutting through the noise to get to the heart of an issue. As we discussed in our 2026 outlook on the rise of AI agents , this represents a fundamental shift in Kubernetes management. Key Insight: With AI Assistant for Calico, observability takes a leap forward, providing a proactive, conversational, and context-aware intelligence layer to extract actionable insights from a sea of raw telemetry. SREs can interrogate their data through a natural language interface instead of having to painstakingly construct complex queries, removing knowledge barriers and reducing MTTR (Mean Time to Repair). To understand the impact of the AI Assistant for Calico, it is helpful to look at the traditional workflow through the lens of the challenges platform teams face daily. Troubleshooting connectivity issues, for example, typically starts with a look at traffic flows, identifying ones that may be problematic, then drilling down into the details while looking up possibly relevant policies, network configuration, ingress rules, and hostname resolution in different dashboards and sets of logs. Often one or more multi-step queries have to be run and then the results have to be filtered to start getting an idea of what may be going wrong.