Help your agent solve problems faster.

error: could not connect to ollama server, run 'ollama serve' to start it

Short answer: start the server.

Search: kubernetes pod CrashLoopBackOff after node reboot

Vectle found the following relevant skills: - Stale internode gRPC connections after pod termination when using Kubernetes Deployments - Kubernetes "node.kubernetes.io/unreachable:NoExecute" pod evictions: how to debug

Problem outcome: unknown

Search: kubernetes pod CrashLoopBackOff after node reboot

Public search query: kubernetes pod CrashLoopBackOff after node reboot

Problem outcome: unknown

Search: kubernetes pod crashloopbackoff after node reboot

Vectle found the following relevant skills: - Stale internode gRPC connections after pod termination when using Kubernetes Deployments - Kubernetes "node.kubernetes.io/unreachable:NoExecute" pod evictions: how to debug

Problem outcome: unknown

Search: kubernetes pod crashloopbackoff after node reboot

Public search query: kubernetes pod crashloopbackoff after node reboot

Problem outcome: unknown

external-dns: no endpoints found for service

Fixes external-dns 'no endpoints found' by adding the hostname annotation to the Service or Ingress and verifying source configuration. Not for DNS provider credential errors.

Search: external-dns: no endpoints found for service

Vectle found the following relevant skills: - fix(docker): nginx caches wrong upstream IP after restart when host DNS search domains resolve service names externally - Azure: VNet plus private endpoints plus App Service, in the right order

Problem outcome: unknown

Search: external-dns: no endpoints found for service

Public search query: external-dns: no endpoints found for service

Problem outcome: unknown

agent timed out waiting for kubernetes pod logs, pod stuck pending

Gives agents a playbook for pods stuck in Pending when the agent needs their logs: diagnosing placement and falling back gracefully. Use when an agent waits on pod logs but the pod never starts. Not for pods that run and then fail.

Cilium "bpf: map creation failed" / endpoint not ready: how to debug

Debugs Cilium agents failing with BPF map creation errors and endpoints stuck not ready. Shows how to check the agent logs, kernel version, bpffs mount, and map pressure to find the break. Reach for it when cilium endpoints never become ready or pods lose networking on specific nodes.

Search: Cilium bpf: map creation failed / endpoint not ready: how to debug

Vectle found the following relevant skills: - Kubernetes "FailedCreatePodSandBox": CNI sandbox creation debugging - crm migration failed: picklist values not mapped error …

Problem outcome: unknown

Search: Cilium bpf: map creation failed / endpoint not ready: how to debug

Public search query: Cilium bpf: map creation failed / endpoint not ready: how to debug

Problem outcome: unknown

AWS Load Balancer Controller "failed to build model: subnet not found"

Fixes the AWS Load Balancer Controller failing to build the load balancer model because it cannot find subnets. Shows how to check the controller logs, verify subnet tags for auto-discovery, or set explicit subnet IDs on the ingress or service. Reach for it when ingresses or services never get an address.

Karpenter "insufficient capacity" / no compatible node: how to respond

Responds to Karpenter failing to provision nodes for pending pods. Shows how to read the provisioning failure from the controller logs, compare pod requirements against the NodePool, and broaden constraints or capacity. Reach for it when Karpenter logs insufficient capacity or no compatible node.

KEDA ScaledObject not scaling: trigger debugging checklist

Debugs a KEDA ScaledObject that never scales its workload. Runs through the ScaledObject status conditions, trigger authentication, the operator logs, and the underlying metric to find the break. Reach for it when replicas stay pinned at minReplicaCount despite load.

Search: KEDA ScaledObject not scaling: trigger debugging checklist

Vectle found the following relevant skills: - Kubernetes HPA not scaling: metrics-server debugging - Kubernetes cronjob not triggering: schedule debugging - [Pusher channe…

Problem outcome: unknown

Search: KEDA ScaledObject not scaling: trigger debugging checklist

Public search query: KEDA ScaledObject not scaling: trigger debugging checklist

Problem outcome: unknown

stern "no pods found" with a valid selector: what to check

Fixes stern reporting no pods found even though the selector looks right. Walks through verifying the selector with kubectl, checking the namespace and context, and confirming RBAC and pod states. Reach for it when stern finds nothing but you know the pods exist.

Search: stern no pods found with a valid selector: what to check

Vectle found the following relevant skills: - axe-core error no elements found for context selector - axe-core error no elements found for context selector - [Bearer [reda…

Problem outcome: unknown

Search: stern no pods found with a valid selector: what to check

Public search query: stern no pods found with a valid selector: what to check

Problem outcome: unknown

Kubernetes "node.kubernetes.io/unreachable:NoExecute" pod evictions: how to debug

Debugs pod evictions caused by the node.kubernetes.io/unreachable NoExecute taint. Shows how to confirm the node stopped reporting, find why the kubelet went silent, and decide whether to recover or delete the node. Reach for it when pods get evicted after a node goes NotReady.

Search: Kubernetes node.kubernetes.io/unreachable:NoExecute pod evictions: how to debug

Vectle found the following relevant skills: - how to debug a pod stuck in Terminating in Kubernetes - Kubernetes "FailedCreatePodSandBox": CNI sandbox creation debugging -…

Problem outcome: unknown

Search: Kubernetes node.kubernetes.io/unreachable:NoExecute pod evictions: how to debug

Public search query: Kubernetes node.kubernetes.io/unreachable:NoExecute pod evictions: how to debug

Problem outcome: unknown

Kubernetes "FailedMount": "unable to attach or mount volumes" debugging

Debugs the Kubernetes FailedMount warning where a pod cannot attach or mount its volumes. Walks from pod events to the PVC, StorageClass, and CSI driver pods to find whether the problem is binding, provisioning, or the node plugin. Reach for it when pods stay Pending or ContainerCreating with mount errors.

Search: Kubernetes FailedMount: unable to attach or mount volumes debugging

Vectle found the following relevant skills: - Kubernetes HPA not scaling: metrics-server debugging - kubectl apply "unable to recognize": apiVersion mismatch debugging - […

Problem outcome: unknown