-
Notifications
You must be signed in to change notification settings - Fork 238
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
Bug 1829233: Recreate DNS service upon Octavia upgrade #607
Bug 1829233: Recreate DNS service upon Octavia upgrade #607
Conversation
f8a01eb
to
0fd4ca6
Compare
Verified the DNS service is recreated upon upgrade |
Don't we need bug tied to this if we're planning to backport it? |
9db4d7b
to
5fe5406
Compare
@MaysaMacedo: This pull request references Bugzilla bug 1829233, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In 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. |
When Octavia is upgraded from OSP13 to OSP16 double listeners becomes supported and the load balancers that requires TCP and UDP on same port should be recreated. This commit ensure the DNS service is recreated upon Octavia upgrade.
5fe5406
to
56e5da0
Compare
/retest |
/lgtm |
/approve |
/assign @squeed |
savedOctaviaVersion := semver.MustParse(octaviaVersion) | ||
multipleListenersVersion := semver.MustParse(MinOctaviaVersionWithMultipleListeners) | ||
if !savedOctaviaVersion.Equal(maxOctaviaVersion) && savedOctaviaVersion.LessThan(multipleListenersVersion) && octaviaMultipleListenersSupport { | ||
dnsService := &v1.Service{ |
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.
Will this cause disruption to the cluster?
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.
It will cause a small downtime of few seconds on the DNS resolution, as a new load balancer with the double listeners is getting created. After the load balancer is in place, the cluster should work normally.
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.
with amphora octavia driver I would say not just a few seconds, but around a minute. Note though this only happens upon OpenStack octavia upgrade between octavia version not supporting UDP to the one supporting it -- on the same port as the TCP one.
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.
That is... a bit concerning. What are the end-user expectations around this upgrade?
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.
The path for Octavia upgrade from version 13 to 16 is still in progress.
Octavia team suggestion for the problem being solved here is to make the operator open a support ticket requesting for the upgrade of a Load Balancer. However, we can't rely on that as our approach for enforcing DNS resolution over TCP would be gone as soon as the upgrade happens.
We expect to work on other approaches for this solution to make it more ideal in following releases.
/test e2e-gcp-ovn |
/override ci/prow/e2e-gcp-ovn |
@squeed: Overrode contexts on behalf of squeed: ci/prow/e2e-gcp-ovn In 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. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dulek, knobunc, luis5tb, MaysaMacedo The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
/hold |
/hold cancel |
/test e2e-gcp |
1 similar comment
/test e2e-gcp |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
@MaysaMacedo: All pull requests linked via external trackers have merged: openshift/cluster-network-operator#607. Bugzilla bug 1829233 has been moved to the MODIFIED state. In 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. |
/cherry-pick release-4.4 |
@MaysaMacedo: #607 failed to apply on top of branch "release-4.4":
In 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. |
When Octavia is upgraded from OSP13 to OSP16 double listeners becomes
supported and the load balancers that requires TCP and UDP on same
port should be recreated.
This commit ensure the DNS service is recreated upon Octavia upgrade.