fix_lb_port_forward #2
Open
Conversation
This file contains 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
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.
This PR suggests a fix to an error we're getting where a worker fail the following way :
{"timestamp":"1475780538.338568926","source":"worker","message":"worker.beacon.restarting","log_level":2,"data":{"error":"failed to dial: failed to connect to TSA:%!(EXTRA *net.OpError=dial tcp: too many colons in address XXX.XXX.XXX.XXX:8080:2222)","session":"3"}}It seems the port is hardcoded in the upstream Dockerfile and the exported
$(CONCOURSE_WEB_SERVICE_PORT)variable doesn't override that value as expected.Currently, loading those files in Kubernetes v1.4.0 doesn't work. This fix allows the ssh calls from the workers to traverse the service loadBalancer to reach the TSA.
More information can be found in the issue I opened in my fork.