Add proxy protocol status to reload script output #14256
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Proxy protocol errors are painful to debug. I added the router proxy protocol status to the reload message so that people will see it and it may jog the thought to check that the upstream load balancer (if present) is correctly configured.
|
@openshift/networking PTAL |
|
[merge] |
|
Evaluated for origin merge up to ef436d3 |
|
[Test]ing while waiting on the merge queue |
|
Evaluated for origin test up to ef436d3 |
|
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/1583/) (Base Commit: 2ceece1) |
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/731/) (Base Commit: 218b782) (Image: devenv-rhel7_6247) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proxy protocol errors are painful to debug. I added the router proxy
protocol status to the reload message so that people will see it and
it may jog the thought to check that the upstream load balancer (if
present) is correctly configured.