Skip to content

Make periodic NodeStatus updates cheaper #14733

@gmarek

Description

@gmarek

We're currently sending whole NodeStatuses only to update a Node heartbeat. This a big source of traffic in the cluster, and one of the possible causes of 1000-node cluster failures. We need to extract heartbeat to a new API 'Heartbeat' object with timestamp and object reference only, and make Kubelet/NodeController to use this object instead of NodeStatus to determine health of the Node.

cc: @wojtek-t @lavalamp @bgrant0607 @brendandburns @smarterclayton @timothysc @davidopp @fgrzadkowski

Metadata

Metadata

Labels

area/apiIndicates an issue on api area.area/kubeletarea/nodecontrollerkind/featureCategorizes issue or PR as related to a new feature.lifecycle/activeIndicates that an issue or PR is actively being worked on by a contributor.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/nodeCategorizes an issue or PR as relevant to SIG Node.sig/scalabilityCategorizes an issue or PR as relevant to SIG Scalability.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions