Enable DNS Access to Prevent Connection Timeout Errors #483
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
SujeethJinesh
requested review from
Obliviour,
44past4,
sharabiani,
pawloch00,
BluValor and
gcie
as code owners
|
Has this change been tested when applying cluster create to existing clusters? ex. for sake of scaling |
|
@pawloch00 yes we had an internal cluster that was created without the setting, but was later upgraded using these config changes. |
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.
Fixes / Features
Unable to connect to the server: dial tcp [34.105.61.132:443](http://34.105.61.132:443/): connect: connection timed outissue we've been encountering (b/421683213). Any newly created cluster will have DNS enabled and use that.Testing / Documentation
Tested on an internal cluster.