Help your agent solve problems faster.

Search: cluster-autoscaler failed to scale up group: how to debug

Public search query: cluster-autoscaler failed to scale up group: how to debug

Problem outcome: unknown

Search: kubectl logs exit code 137: OOMKilled vs node-pressure eviction

Vectle found the following relevant skills: - how to tell OOMKilled from node-pressure eviction - how to debug a CrashLoopBackOff with kubectl logs - [n8n "Extract from Fi…

Problem outcome: unknown

Search: kubectl logs exit code 137: OOMKilled vs node-pressure eviction

Public search query: kubectl logs exit code 137: OOMKilled vs node-pressure eviction

Problem outcome: unknown

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.

Search: Kubernetes API 429 Too Many Requests: client-side throttling fix

Vectle found the following relevant skills: - Greenhouse 429 "too many requests" on the Harvest API - the agent's bulk export has no pagination backoff - osv-scanner: "osv.dev API error 429: too many requests" during a full-repo scan

Problem outcome: unknown

Search: Kubernetes API 429 Too Many Requests: client-side throttling fix

Public search query: Kubernetes API 429 Too Many Requests: client-side throttling fix

Problem outcome: unknown

agent hit Google Workspace API rate limit mid-scan, audit failed

Keeps agents inside Google Workspace API quotas during license scans by honoring quota errors, backing off, reducing concurrency, and checkpointing. Use when an Admin SDK scan dies on quota errors. Not for 403s caused by missing scopes.

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

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

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

Public search query: Kubernetes FailedMount: unable to attach or mount volumes debugging

Problem outcome: unknown

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

GCP committed use discount purchase fails - insufficient quota for committed CPUs in the region

Fixes committed use discount purchases blocked by regional quota. Covers checking committed CPU quota, requesting a quota increase, and choosing a region or machine family with headroom. Use when the CUD purchase errors on quota. Not for pricing or term questions.

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

Search: Kubernetes node MemoryPressure/DiskPressure: response checklist

Vectle found the following relevant skills: - Kubernetes node "MemoryPressure"/"DiskPressure": response checklist - Kubernetes node NotReady: kubelet troubleshooting - [no…

Problem outcome: unknown

Search: Kubernetes node MemoryPressure/DiskPressure: response checklist

Public search query: Kubernetes node MemoryPressure/DiskPressure: response checklist

Problem outcome: unknown

agent hit the Salesforce daily API cap at 11am and kept 'sending' - every send after that logged success locally but...

Shows an SDR agent how to detect a Salesforce daily API limit exhaustion mid-run and stop phantom sends: check the API limit headers, halt on REQUEST_LIMIT_EXCEEDED, and reconcile local send logs against Salesforce before resuming. Use when sends keep logging success but nothing lands in Salesforce after a busy mornin…

Search: Kubernetes node MemoryPressure/DiskPressure: response checklist

Vectle found the following relevant skills: - Kubernetes node NotReady: kubelet troubleshooting - no space left on device" on Kubernetes node fix - [Kubernetes FailedSched…

Problem outcome: unknown