Kubernetes on ErrorVault — Developer Error Code Dictionary

Fix k8s-admission-webhook-denied: Admission webhook denied the request validating error

Tue, 14 Jul 2026 17:51:00 +0800

The k8s-admission-webhook-denied error indicates that a Kubernetes API request was intercepted and rejected by an admission webhook. Admission webhooks are a powerful extension mechanism in Kubernetes, allowing cluster administrators to implement custom policies and validations for resources being created, updated, or deleted. When this error occurs, it means that the resource you are attempting to manage does not comply with a policy enforced by one of these webhooks.

1. Symptoms: Clear description of indicators and shell output.

When an admission webhook denies a request, you will typically observe an error message directly from the kubectl command-line tool or within the Kubernetes API server logs. The most common symptom is the failure of a kubectl apply, kubectl create, or kubectl edit command to complete successfully. The output will explicitly state that an admission webhook denied the request, often providing the name of the webhook and a specific reason for the denial.

Fix k8s-evicted: Pod evicted due to ephemeral-storage or memory pressure

Sun, 05 Jul 2026 09:25:00 +0800

When a Kubernetes pod is in an Evicted state, it signifies that the Kubelet, the agent running on each node, has proactively terminated the pod to reclaim resources and maintain node stability. This critical action is typically triggered by resource pressure, most commonly related to ephemeral storage or memory exhaustion. Understanding the precise cause and implementing appropriate resource management strategies are crucial for maintaining a healthy and reliable Kubernetes cluster.

Fix clw-memory-oom: OpenClaw Out of Memory Error Resolution

Sat, 13 Jun 2026 17:32:04 +0800

1. Symptoms

The clw-memory-oom error occurs when an OpenClaw-managed workload exhausts its allocated memory resources. This error manifests through several distinct symptoms that help identify the root cause.

Primary Symptoms:

When the memory limit is reached, the OpenClaw runtime generates a specific error event:

[ERROR] clw-memory-oom: Container workload-xyz exceeded memory limit [ERROR] Current usage: 2048Mi, Limit: 2048Mi [ERROR] Memory allocation request rejected


**Observable Symptoms:**

- **Container restart loops**: The workload container enters an `OOMKilled` state and restarts repeatedly
- **Application crashes**: The process terminates unexpectedly without graceful shutdown
- **Memory metric spikes**: In monitoring dashboards, memory usage graphs show a sharp vertical line at the limit threshold
- **Health check failures**: Liveness probes fail after the container is killed
- **Pod status changes**: In Kubernetes environments, the pod status shows `OOMKilled` or `CrashLoopBackOff`

**Log Output Examples:**

```bash
# OpenClaw runtime logs
2024-01-15T10:23:45.123Z ERROR [runtime] clw-memory-oom detected
2024-01-15T10:23:45.124Z ERROR [runtime] Workload: payment-processor
2024-01-15T10:23:45.125Z ERROR [runtime] Memory stats: used=2147483648 bytes, limit=2147483648 bytes
2024-01-15T10:23:45.126Z INFO [runtime] Initiating graceful termination (timeout: 30s)
2024-01-15T10:23:45.200Z INFO [runtime] Container terminated with signal SIGKILL

# kubectl describe pod output
Name:             payment-processor
Namespace:        production
Status:           OOMKilled
Containers:
  payment-svc:
    Memory:       2148Mi / 2048Mi  # Usage exceeds limit
    Last State:   Terminated
      Reason:     OOMKilled
      Exit Code:  137

2. Root Cause

The clw-memory-oom error stems from a fundamental mismatch between memory consumption and memory allocation. Understanding the underlying causes is essential for implementing an effective solution.