WhatBrokeToday
GTA 6FAQ
Kubernetes

Kubernetes PodReadyToStartContainers Condition Lacks Sandbox Creation Error Details

minor

Is it fixed? Not yet.

Ongoing since Nov 10, 18:19 UTC. First reported Nov 10, 18:19 UTC.

What happened

When pod sandbox creation fails, the PodReadyToStartContainers condition's Message field does not include the specific error details from the failed attempt, such as a CNI ADD error. Users must currently look to FailedCreatePodSandBox events on the pod to find the failure reason.

What caused it?

The PodReadyToStartContainers condition reports the state of the sandbox (e.g., 'no pod sandbox exists') but fails to include the underlying error message from the failed sandbox creation attempt.

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on GitHub issue

    PodReadyToStartContainers condition should include sandbox creation error details

    Source

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    PodReadyToStartContainers condition should include sandbox creation error details(opens GitHub issue in a new tab)

    What happened? When pod sandbox creation fails (e.g., due to a CNI ADD error), the failure detail is only available in FailedCreatePodSandBox events on the pod. The PodReadyToStartContainers condition — which was specifically designed to surface sandbox readiness — does not include the error from the failed sandbox creation attempt. After #135300, the condition's Message field reports what state the sandbox is in (e.g., "no pod sandbox exists", "pod sandbox has no IP address"), but not why it…

    by akalenyu 0upvotes 3comments

FAQ

What happened in the Kubernetes outage?

When pod sandbox creation fails, the PodReadyToStartContainers condition's Message field does not include the specific error details from the failed attempt, such as a CNI ADD error. Users must currently look to FailedCreatePodSandBox events on the pod to find the failure reason.

What is affected by the Kubernetes outage?

Kubernetes.

When did the Kubernetes outage start and end?

It started Nov 10, 18:19 UTC and is still ongoing (8 d 10 h so far). This page updates as it develops.

How do I get alerts for Kubernetes?

Subscribe to the Kubernetes RSS feed for every new Kubernetes incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Kubernetes is down. Kubernetes feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.