WhatBrokeToday
Technology directory

Kubernetes

DevOps & Tools

Container orchestration platform.

kubernetes.io

30-day hazard rating

Elevated5.3 / 10
Incidents (30d)
8
Severity-weighted volume
9.0
Critical / high (clustered)
0 / 1
Avg time to resolve
n/a

Volume of incidents (weighted by severity) over the last 30 days, raised when fixes are slow. 1 = calm, 10 = constant breakage.

Incidents, 30 days
8
Reports, 30 days
8
Active advisories
8
Regression lifespan
n/a
nothing resolved yet

Incidents per day, last 30 days

0246Oct 9Oct 23Nov 7
View as table
Kubernetes incidents per day, last 30 days
DateIncidentsReports
2026-11-0733
2026-11-0655
2026-11-0500
2026-11-0400
2026-11-0300
2026-11-0200
2026-11-0100
2026-10-3100
2026-10-3000
2026-10-2900
2026-10-2800
2026-10-2700
2026-10-2600
2026-10-2500
2026-10-2400
2026-10-2300
2026-10-2200
2026-10-2100
2026-10-2000
2026-10-1900
2026-10-1800
2026-10-1700
2026-10-1600
2026-10-1500
2026-10-1400
2026-10-1300
2026-10-1200
2026-10-1100
2026-10-1000
2026-10-0900

Active advisories

  3. mediumInvestigating

    Kubernetes Device Manager Checkpoint State Desynchronizes on Admission Failure

    During Pod admission, kubelet's Device Manager assigns physical device IDs and checkpoints the state to disk, but if container admission subsequently fails and the kubelet is restarted, the device checkpoint state can desynchronize.

    Kubernetes

    since 11 h 22 min

    Velocity
    3.2
  4. mediumInvestigating

    Kubernetes ResourceClaim Updates Fail Due to Non-Canonical JSON Opaque Parameters

    ResourceClaim updates fail with a 'spec: field is immutable' error when opaque parameters are not in canonical JSON format, such as when created via the Python client. The issue occurs because the apiserver re-encodes JSON fields, causing a byte mismatch during the immutable spec check.

    Kubernetes

    since 1 d 2 h

    Velocity
    2.5
  5. mediumInvestigating

    Kubernetes Concurrent Watch Decoder Goroutine Panic Handling Issues

    An issue was discovered in Kubernetes where adding HandleCrash calls to the concurrent watch decoder's goroutines caused callers to wait indefinitely if a worker recovered from a panic without publishing a result. Recovery mechanisms must ensure failures are properly reported so callers can finish execution.

    Kubernetes

    since 1 d

    Velocity
    2.3
  6. mediumInvestigating

    Kubernetes List Requests with Limit and Field Selector Return Latest Revision Instead of Exact ResourceVersion

    List requests with a limit and resourceVersion, without resourceVersionMatch, are incorrectly served at the latest revision rather than the requested exact revision when the field selector targets a single object. This affects API queries for single objects like ConfigMaps by name, returning current data and the wrong resourceVersion.

    Kubernetes

    since 1 d 1 h

    Velocity
    2.1
  7. mediumInvestigating

    Kubernetes Server-Side Apply Status Subresource Incorrectly Acquires Root Field Ownership

    Server-Side Apply on a CRD's /status subresource can acquire ownership of an unchanged, non-status root field that the status strategy restores from the old object. This causes subsequent changes by the original main-endpoint manager to conflict with the unintended status ownership.

    Kubernetes

    since 1 d 2 h

    Velocity
    1.6
  8. mediumInvestigating

    Kubernetes Kubelet: Node /etc/hosts Entries Shadow hostAliases in hostNetwork Pods

    In hostNetwork: true Pods, kubelet writes the node's /etc/hosts entries before appending spec.hostAliases. Consequently, when the node already contains an entry for the same hostname, lookups resolve to the node's IP first rather than the intended hostAlias IP.

    Kubernetes

    since 1 d 12 h

    Velocity
    1.3

Version hazard notices

No version-specific incidents for Kubernetes in the last 90 days.

Resolved incident history

No resolved incidents on record yet.