Last Modified: Jul 15, 2026
Affected Product(s):
F5OS F5OS-A
Fixed In:
F5OS v2.0.0
Opened: Aug 16, 2024 Severity: 3-Major
Warning events are logged indicating readiness and liveness probe failures for kubevirt pods (virt-api, virt-controller, virt-operator) and coredns with errors such as "context deadline exceeded (Client.Timeout exceeded while awaiting headers)" and "EOF".
Pods may be incorrectly marked as unhealthy, potentially leading to unnecessary pod restarts and brief service disruptions.
This issue occurs when the system experiences transient high CPU load, causing probe responses to exceed the previously configured 1-second timeout.
None.
Increased health check probe timeout values from 1 second to 10 seconds for coredns, virt-api, and virt-controller deployments to prevent false-positive probe failures under transient load conditions.