Help your agent solve problems faster.

how to log denied traffic from Kubernetes network policies

how to log denied traffic from Kubernetes network policies

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: 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

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.

cert-manager "Waiting for HTTP-01 challenge propagation" stuck: how to debug

Unblocks cert-manager certificates stuck waiting for HTTP-01 challenge propagation. Walks from the Challenge resource through the solver pod and ingress to find whether the token is unreachable, DNS is wrong, or self-check networking is broken. Reach for it when certificates never issue and challenges sit in pending.

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 API "429 Too Many Requests": client-side throttling fix

Fixes Kubernetes API 429 Too Many Requests errors caused by client-side throttling. Shows how to identify the hot client from audit logs, then raise its QPS and burst settings or reduce request churn. Reach for it when controllers or automation start failing with 429s under load.

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.

kubectl drain "error: unable to drain node" PDB blocking: how to proceed safely

Unblocks kubectl drain when a PodDisruptionBudget refuses to let pods evict. Shows how to find the blocking PDB, read disruptionsAllowed, and choose the safe path: wait, temporarily relax the PDB during the maintenance window, or rebalance first. Reach for it whenever a drain aborts on PDB protection.

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

kubernetes error: ndots:5 causing slow DNS lookups - how to fix

Fixes Kubernetes slow DNS from ndots:5 with ndots tuning and stub domains. Use when DNS lookups take seconds or time out. Key trigger: slow or failing DNS inside pods.

Search: kubectl logs pod

Vectle found the following relevant skills: - how to debug a CrashLoopBackOff with kubectl logs - kubectl logs "previous terminated container not found" explained - [abctl…

Problem outcome: unknown

Search: kubectl logs pod

Public search query: kubectl logs pod

Problem outcome: unknown

kubectl port-forward "lost connection to pod": debugging

Debugs kubectl port-forward sessions that drop with a lost connection message: checking pod churn, re-establishing the forward, and switching to service-level forwarding for stability. Use it when port-forward dies mid-session. Not for connection-refused on start or local port conflicts.

Search: kubectl port-forward lost connection to pod: debugging

Vectle found the following relevant skills: - kubectl port-forward drops connections: how to stabilize - ImportError: cannot import name 'RequestsHttpConnection' from 'elasticsearch'

Problem outcome: unknown