DFDS IT incident
Problematic node on hellman Kubernetes cluster must be killed
Resolved after 28 minutes, affecting Kubernetes [Hellman] - Capacity/Scheduling, on February 13, 2026.
All workloads on the faulty node have now started up on a new node.
Affected components
Update timeline
- investigating Feb 13, 2026, 12:35 PM UTC
We are currently investigating this issue.
- identified Feb 13, 2026, 12:37 PM UTC
The node is cordoned off and now marked as unhealthy. Once a new node has been started up, we will start draining all the workloads on this node. The root cause is the kubelet having problems with managing Pod lifecycle, in particular termination, so if draining adds to the problem, all workloads on that node will be forcefully terminated. Downtime can be expected.
- monitoring Feb 13, 2026, 12:46 PM UTC
All workloads on the faulty node have now started up on a new node.
- resolved Feb 13, 2026, 01:04 PM UTC
This incident has been resolved.
Your product runs on more than DFDS IT
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services