Skip to content

Some Nodes didn't register during cluster startup #24794

Closed
@gmarek

Description

http://kubekins.dls.corp.google.com/view/Scalability/job/kubernetes-e2e-gce-enormous-cluster/112/consoleFull

09:12:35 Detected 998 ready nodes, found 998 nodes out of expected 1001. Your cluster may not be fully functional.

We currently allow some Nodes to be NotReady during cluster startup, but we still require all of them to be registered. Do we want to change the logic to allow not registered Nodes as well? @davidopp Do we know why Nodes didn't registered? @dchen1107

Metadata

Assignees

Labels

lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.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.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions