Open
Conversation
Member
michaeljguarino
left a comment
There was a problem hiding this comment.
This pr seems confused to me. A few things:
- We always publish the information of the management dns zone to the management clusters service context, you're trampling that here. it's needed to make sure other wiring works (why there's three service contexts).
- If you're creating additional dns zones, use them wherever needed, so make them be published down to the dev/prod networks if so.
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
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.
The core-infra stack was reusing the dev/prod db dns zones created on the mgmt cluster. This PR creates a new set and optionally reads from the mgmt cluster if the
use_mgmt_dns_zonevar on core-infra istrue; defaults tofalse