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
Bugs 1884421,1884422: Backport router hostindex fixes #25578
Bugs 1884421,1884422: Backport router hostindex fixes #25578
Conversation
Ensure that a passthrough route displaces any path-based TLS routes with the same host, because passthrough is incompatible with path-based routing. This commit fixes bug 1691190. https://bugzilla.redhat.com/show_bug.cgi?id=1691190 * pkg/router/controller/hostindex/activation.go (hasExistingMatch): Return true if both routes are TLS and the existing route is a passthrough route. * pkg/router/controller/hostindex/hostindex_test.go (Test_hostIndex): Verify that a passthrough route displaces path-based TLS routes with the same host, but does not displace non-TLS routes.
Just as a passthrough route displaces any path-based TLS routes with the same host, a path-based TLS route displaces any passthrough route with the same host. Follow-up to commit 65e784fe491ef02c4db0346348e6ac6192d68e30. * pkg/router/controller/hostindex/activation.go (hasExistingMatch): Return true if both routes are TLS and *either* route is passthrough. * pkg/router/controller/hostindex/hostindex_test.go (Test_hostIndex): Verify that a path-based TLS route displaces passthrough routes with the same host.
Before this patch, inactive routes were not being promoted when the conflicting routes were deleted. Fix it so that when deletes happen, all inactive routes are given a chance to be promoted.
|
@Miciah: No Bugzilla bug is referenced in the title of this pull request. 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. |
|
@Miciah: No Bugzilla bug is referenced in the title of this pull request. 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. |
|
/test unit |
|
@Miciah: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
@Miciah unit tests are known to be very flakey on 3.11 right now |
Known flakes and fixes: 3.11 related BZs to address the flakes are: |
|
/test unit |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Miciah, sgreene570 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. |
4 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
/test extended_conformance_install |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
5 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
19 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@Miciah: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
/hold Looking into the failures. |
|
Ansible fails on restarting the node. The /test extended_conformance_install |
|
Tests are all green, but some of them last ran in November, so let's rerun tests and try to get this PR approved. |
|
/hold cancel |
Backport openshift/router#57, openshift/router#59, and openshift/router#126 (modulo potentially incompatible changes related to unit tests).
hostindex: Passthrough displaces path-based TLS
Ensure that a passthrough route displaces any path-based TLS routes with the same host, because passthrough is incompatible with path-based routing.
pkg/router/controller/hostindex/activation.go(hasExistingMatch): Return true if both routes are TLS and the existing route is a passthrough route.pkg/router/controller/hostindex/hostindex_test.go(Test_hostIndex): Verify that a passthrough route displaces path-based TLS routes with the same host, but does not displace non-TLS routes.hostindex: Path-based TLS displaces passthrough
Just as a passthrough route displaces any path-based TLS routes with the same host, a path-based TLS route displaces any passthrough route with the same host.
pkg/router/controller/hostindex/activation.go(hasExistingMatch): Return true if both routes are TLS and either route is passthrough.pkg/router/controller/hostindex/hostindex_test.go(Test_hostIndex): Verify that a path-based TLS route displaces passthrough routes with the same host.Try to promote inactive routes following route deletion
Before this patch, inactive routes were not being promoted when the conflicting routes were deleted. Fix it so that when deletes happen, all inactive routes are given a chance to be promoted.