[GCP IMDS] Use fully qualified name #2060
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.
Use the fully-qualified name for the GCP IMDS endpoint
Description
This PR replaces the current IMDS endpoint
http://metadata/computeMetadata/v1/...with the fully-qualified name versionhttp://metadata.google.internal/computeMetadata/v1/....The current state assumes the presence of
google.internalas a search domain to work properly which may not be the case when the endpoint is resolved from a container or a Kubernetes pod running on a GCP node.Status
ready for review
Checklist (tick everything that applies)