Skip to content
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

move clearInitialNodeNetworkUnavailableCondition to clustermanager #3856

Merged

Conversation

JacobTanenbaum
Copy link
Contributor

clearInitialNodeNetworkUnavailableCondition needs to be run on every node for GCP. Since we have some nodes that are not running ovn-kubernetes, notably windows, it should be run in the clustermanager

- What this PR does and why is it needed

- Special notes for reviewers

- How to verify it

- Description for the changelog

@JacobTanenbaum
Copy link
Contributor Author

@dcbw PTAL

@JacobTanenbaum JacobTanenbaum force-pushed the fixClearInitialCondition branch 2 times, most recently from e5cab88 to b582cfe Compare August 24, 2023 14:14
clearInitialNodeNetworkUnavailableCondition needs to be run on every
node for GCP. Since we have some nodes that are not running
ovn-kubernetes, notably windows, it should be run in the clustermanager

Signed-off-by: Jacob Tanenbaum <[email protected]>
@trozet trozet merged commit 05fbd0b into ovn-kubernetes:master Aug 24, 2023
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants