-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a NodeCondition "NetworkUnavailable" to prevent scheduling onto a node until the routes have been created #26415
Add a NodeCondition "NetworkUnavailable" to prevent scheduling onto a node until the routes have been created #26415
Conversation
2e49da0
to
18652e3
Compare
There is currently a problem with this PR - kubelet is overwriting node status written by route controller. |
Actually something different is happening here. Investigating. |
18652e3
to
8623c54
Compare
OK - debugged and fixed. Hopefully tests will pass now. |
This looks better to me. @kubernetes/rh-networking - please take a pass. |
@@ -2009,6 +2009,8 @@ const ( | |||
NodeOutOfDisk NodeConditionType = "OutOfDisk" | |||
// NodeMemoryPressure means the kubelet is under pressure due to insufficient available memory. | |||
NodeMemoryPressure NodeConditionType = "MemoryPressure" | |||
// NodeNetworkingNotReady means that network for the node is not correctly configured. | |||
NodeNetworkingNotReady NodeConditionType = "NetworkingNotReady" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer "NetworkUnavailable".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed.
8623c54
to
be1b571
Compare
@bgrant0607 - thanks a lot for quick review. Comments applied. PTAL BTW - do we need want a release note for this? |
LGTM |
Thanks @bgrant0607 ! |
LGTM |
GCE e2e build/test passed for commit be1b571. |
Automatic merge from submit-queue |
@wojtek-t Does this PR require action by the user when upgrading from 1.2.x to 1.3.0? (Think about non-developer users.) If so, please edit your first comment to have a release-note block, like in #28132. If it is just an optional feature, please change the label to just release-note. If it is not a complete feature by itself, then apply "release-note-none" label instead. |
This is new version of #26267 (based on top of that one).
The new workflow is:
Release Note
@gmarek @bgrant0607 @zmerlynn @cjcullen @derekwaynecarr @danwinship @dcbw @lavalamp @vishh