Add support for GKE DNS-based endpoints #8630
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
[upstream:c6e460de8cef5f79f307c65095447b04f859e1d5] Signed-off-by: Modular Magician <[email protected]>
modular-magician
deleted the
downstream-pr-c6e460de8cef5f79f307c65095447b04f859e1d5
branch
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.
Add support for GKE DNS-based endpoints
Uses the newly introduced ControlPlaneEndpointsConfig message in the underlying GKE API calls, avoiding using deprecated fields. Support for the IPEndpointsConfig subfield, along with migration of related PrivateClusterConfig fields, will follow.
Derived from GoogleCloudPlatform/magic-modules#12195