[release-4.7] Bug 2047325: Fix node connectivity to service backed by egress IP pods#946
Conversation
|
@flavio-fernandes: This pull request references Bugzilla bug 2047325, which is invalid:
Comment 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. |
|
/bugzilla refresh |
|
@flavio-fernandes: This pull request references Bugzilla bug 2047325, which is invalid:
Comment 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. |
|
/retest |
|
oh. thanks! -- flaviof |
Legacy commit using ovn-nbctl for the implementation. This commit will be used for backports to older versions. The host network couldn't connect to services backed by egress IP matching pods since the return packets would get forwarded to the egress nodes for these pods because of the routing policies specified for the egress matching pods. This would in turn break the connection. Hence what we need is to specify routing policies which forces the packet to go to the originating GR instead of getting routed to the egress node GR. Conflicts: go-controller/pkg/ovn/egressip.go go-controller/pkg/ovn/egressip_test.go Signed-off-by: Flavio Fernandes <flaviof@redhat.com> Co-authored-by: Alexander Constantinescu <aconstan@redhat.com> (cherry picked from commit 49f4fef)
5bfa199 to
4e50fc5
Compare
|
|
/bugzilla refresh |
|
@flavio-fernandes: This pull request references Bugzilla bug 2047325, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
Requesting review from QA contact: 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. |
|
@flavio-fernandes: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
/assign @trozet |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flavio-fernandes, trozet The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
9 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
hello @anuragthehatter @zhaozhanqi. Can you look into adding the cherry-pick-approved label to this pr, please? |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/label qe-approved |
|
/label cherry-pick-approved |
|
@flavio-fernandes: All pull requests linked via external trackers have merged: Bugzilla bug 2047325 has been moved to the MODIFIED state. 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 is a cherry-pick of #886
Legacy commit using ovn-nbctl for the implementation. This commit will
be used for backports to older versions.
The host network couldn't connect to services backed by egress IP
matching pods since the return packets would get forwarded to the egress
nodes for these pods because of the routing policies specified for the
egress matching pods. This would in turn break the connection. Hence
what we need is to specify routing policies which forces the packet to
go to the originating GR instead of getting routed to the egress node
GR.
Conflicts:
go-controller/pkg/ovn/egressip_test.go
Signed-off-by: Flavio Fernandes flaviof@redhat.com
Co-authored-by: Alexander Constantinescu aconstan@redhat.com
(cherry picked from commit 49f4fef)