-
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
Add an ENV to control ipv6 behavior in the router #15351
Add an ENV to control ipv6 behavior in the router #15351
Conversation
This patch adds an environent variable called ROUTER_IP_V4_V6_MODE which must be set to "v4" (the default), "v6", or "v4v6" to control whether the router to binds to IPv4, IPv6, or both. Note that when set to 'v6' or 'v4v6', the X-Forwarded-For and Forwarded http headers will be in IPv6 form (even when the connection was an IPv4 one, if set to 'v4v6'). Back-port of openshift#15229 Fixes bug 1472976 (https://bugzilla.redhat.com/show_bug.cgi?id=1472976)
@openshift/networking FYI |
[test][testextended][extended: networking] |
[test] last flaked on #15337 |
[merge][severity: blocker] This has passed each test cleanly... just not on the same run. i.e. each run has flaked in different places. |
continuous-integration/openshift-jenkins/merge Waiting: You are in the build queue at position: 3 |
Evaluated for origin merge up to 19208a5 |
[test] flaked on #15351 |
Evaluated for origin testextended up to 19208a5 |
continuous-integration/openshift-jenkins/testextended SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended/890/) (Base Commit: b7540a5) (PR Branch Commit: 19208a5) (Extended Tests: networking) |
[test] flaked on docker pull with |
sdnnamespace flake fix merged, [test] |
[test] flaked on #15401 |
Evaluated for origin test up to 19208a5 |
continuous-integration/openshift-jenkins/test Running (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/3384/) (Base Commit: 787f4e2) (PR Branch Commit: 19208a5) |
This patch adds an environent variable called ROUTER_IP_V4_V6_MODE
which must be set to "v4" (the default), "v6", or "v4v6" to control
whether the router to binds to IPv4, IPv6, or both.
Note that when set to 'v6' or 'v4v6', the X-Forwarded-For and
Forwarded http headers will be in IPv6 form (even when the connection
was an IPv4 one, if set to 'v4v6').
Back-port of #15229
Fixes bug 1472976 (https://bugzilla.redhat.com/show_bug.cgi?id=1472976)