-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
router: fix ingress compatibility with f5 #12843
Conversation
f5 needs the same name conversion already used for haproxy to ensure that the names of routes generated from ingresses can be used safely.
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.
LGTM. Thanks @marun
[test] |
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.
LGTM
[merge] |
[test] |
Evaluated for origin test up to 7ebb613 |
continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/13675/) (Base Commit: bcddac6) |
[merge] |
Evaluated for origin merge up to 7ebb613 |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/13723/) (Base Commit: 421e4d0) (Image: devenv-rhel7_5881) |
f5 needs the same name conversion already used for haproxy to ensure that the names of routes generated from ingresses can be used safely.
cc: @openshift/networking