Tale of a Kubernetes node-feature-discovery incident
Read OriginalA detailed post-mortem of a Kubernetes incident where upgrading the node-feature-discovery (NFD) component caused major scale issues. The new version's architectural shift to using NodeFeature custom resources consumed excessive etcd storage (~140 KB per node) in large production clusters, breaking pod scheduling. The article covers the decision to roll back and provides lessons on evaluating off-the-shelf components for large-scale operations.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
1
2
Better react-hook-form Smart Form Components
Maarten Hus
•
2 votes
3
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook
•
1 votes
4
Quoting Thariq Shihipar
Simon Willison
•
1 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft
•
1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop
•
1 votes