-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Add information about octavia upgrades impact on Kuryr SDN #21488
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 information about octavia upgrades impact on Kuryr SDN #21488
Conversation
|
@luis5tb And this one is 4.5+, right? |
right! |
MaysaMacedo
left a comment
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.
Looks great! Just few nits and a question.
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.
Even though it's really likely that this will happen, have we check it?
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.
No, I'll do as soon as I get access to an env where I can test it
f5e09d0 to
91ab5dd
Compare
|
Looks good. Should we add a note about the DNS service recreation on the CNO? |
91ab5dd to
3f991e2
Compare
done |
|
/lgtm |
|
/lgtm |
|
New changes are detected. LGTM label has been removed. |
|
Tweaked to fix parallel construction error. Nothing substantive. |
|
LGTM. Don't forget to squash your commits. :) |
Always! Thanks! |
|
/cherry-pick enterprise-4.5 |
|
@maxwelldb: new pull request created: #22787 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This PR adds information about the octavia upgrades problems with using Kuryr SDN, depending on the way OSP handles them