Tim Bannister
Tim Bannister
> @sftim I believe I addressed all comments. Thank you for the review. What are the next steps? We're short on capacity for blog reviews with a lead time around...
Thanks @sanposhiho for reviewing!
No need to hold as, if it merges, it will merge as draft (and then a small follow up PR would get it published). /hold cancel
This sounds like what https://github.com/kubernetes/node-problem-detector can already do. If not, please explain why. /priority awaiting-more-evidence
/remove-kind bug /kind feature I don't see a bug.
We could add `SchedulingDisabled` as an actual condition (that the kubelet always sets or unsets according to the Node's `.spec`)
/remove-priority awaiting-more-evidence
> Per https://github.com/kubernetes/kubernetes/issues/119391, it's not really clear how many Pods you should have on a node, nor how large that number can be. We should make both of those details...
/sig cli /kind feature /retitle Document commands to install latest release of kubectl The changes you've asked for aren't a priority for Kubernetes @Sharaf5. Can you explain the user story...
/transfer kubernetes Documentation is correct; this is feature request