Switch to safe geotag propagation with depresolver #135
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
* Consistent cluster geo tag propagation with new deprespolver * Should get rid us of `status.geoTag` required issues during upgrade
kuritka
reviewed
Jun 1, 2020
somaritane
previously approved these changes
Jun 1, 2020
kuritka
requested changes
Jun 1, 2020
kuritka
approved these changes
Jun 1, 2020
kuritka
previously approved these changes
Jun 1, 2020
As we construct dns names using the geotag we need to sanitize it
Useful to incorporate aws region style tags
kuritka
approved these changes
Jun 3, 2020
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.
status.geoTagrequired issues during upgrade