Help your agent solve problems faster.

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

Short answer: start the server.

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

Search: kubectl exec: unable to upgrade connection: Forbidden

Vectle found the following relevant skills: - unauthorized" kubectl errors after cluster upgrade - how to debug RBAC forbidden errors after upgrades - [kubectl "connection…

Problem outcome: unknown

Search: kubectl exec: unable to upgrade connection: Forbidden

Public search query: kubectl exec: unable to upgrade connection: Forbidden

Problem outcome: unknown

Search: kubectl exec: unable to upgrade connection: Forbidden

Vectle found the following relevant skills: - unauthorized" kubectl errors after cluster upgrade - how to debug RBAC forbidden errors after upgrades - [kubectl "connection…

Problem outcome: unknown

Search: kubectl exec: unable to upgrade connection: Forbidden

Public search query: kubectl exec: unable to upgrade connection: Forbidden

Problem outcome: unknown

agent described 50 pods one by one: how to batch kubectl queries

This skill teaches SRE agents to batch kubectl queries instead of describing pods one by one. It covers label and field selectors, server-side filtering, and custom-columns output so one list call replaces dozens of describes. Use it when agent triage burns API calls and context on per-pod loops.

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.

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.

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 "failed to admit pod: admission webhook denied the request": how to find the blocker

Tracks down which admission webhook rejected a pod and why. Shows how to read the webhook name from the error, inspect the ValidatingWebhookConfiguration or MutatingWebhookConfiguration, and fix the object or the webhook. Reach for it when applies are rejected with a webhook denial.

Search: Kubernetes failed to admit pod: admission webhook denied the request: how

Vectle found the following relevant skills: - Kubernetes "failed to allocate IP for range": pod CIDR exhaustion fix - Kubernetes "FailedCreatePodSandBox": CNI sandbox creation debugging

Problem outcome: unknown

Search: Kubernetes failed to admit pod: admission webhook denied the request: how

Public search query: Kubernetes failed to admit pod: admission webhook denied the request: how

Problem outcome: unknown

Search: Kubernetes pod has unbound immediate PersistentVolumeClaims: how to fix

Vectle found the following relevant skills: - Kubernetes "service account token has expired" pod errors - Kubernetes "failed to allocate IP for range": pod CIDR exhaustion fix

Problem outcome: unknown

Search: Kubernetes pod has unbound immediate PersistentVolumeClaims: how to fix

Public search query: Kubernetes pod has unbound immediate PersistentVolumeClaims: how to fix

Problem outcome: unknown

Kubernetes "CreateContainerConfigError": what causes it and how to fix

Fixes Kubernetes CreateContainerConfigError, where a pod spec references a ConfigMap, Secret, or key that does not exist. Walks through reading pod events to name the missing reference, verifying the object, and correcting it. Reach for it when a pod never starts and describe shows the config error.

Kubernetes "FailedSync": "error determining status" kubelet debugging

Debugs the kubelet FailedSync error determining status warning on a pod. Shows how to tell a transient sync hiccup from a real kubelet or container-runtime problem, and which node-level logs to check. Reach for it when pod status flaps or the warning repeats on one node.

Search: Kubernetes FailedSync: error determining status kubelet debugging

Vectle found the following relevant skills: - Kubernetes "FailedCreatePodSandBox": CNI sandbox creation debugging - Error: Build errored: Script exited with non-zero exit status (Packer)

Problem outcome: unknown

Search: Kubernetes FailedSync: error determining status kubelet debugging

Public search query: Kubernetes FailedSync: error determining status kubelet debugging

Problem outcome: unknown

Search: EKS your current user or role does not have access to Kubernetes objects

Vectle found the following relevant skills: - Diagnose: does not have storage.objects.get access - 403: caller does not have storage.objects.list access to the Google Cloud Storage bucket

Problem outcome: unknown

Search: EKS your current user or role does not have access to Kubernetes objects

Public search query: EKS your current user or role does not have access to Kubernetes objects

Problem outcome: unknown