k8s: use the metadata client to fetch metadata, instead of full objects #3851
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
I was pulling in the metadata client to help with #3845, and this seemed like a good optimization to do while I was here
|
see notes on https://pkg.go.dev/k8s.io/client-go/metadata/#Client, seems like this got introduced in Kubernetes 1.14, and the client will emulate pre-1.14 behavior |
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.
Hello @landism, @maiamcc,
Please review the following commits I made in branch nicks/metadata:
f773fe2 (2020-10-12 16:47:16 -0400)
k8s: use the metadata client to fetch metadata, instead of full objects
I was pulling in the metadata client to help with #3845,
and this seemed like a good optimization to do while I was here
Code review reminders, by giving a LGTM you attest that: