Support for metadata-only fetches in k8s_info module #1030
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.
SUMMARY
This pull request adds support for a new
metadata_onlyoption ink8s_infomodule, enabling support for K8S API Metadata-only fetches.This helps reducing memory footprint when retrieving large collections of objects.
ISSUE TYPE
COMPONENT NAME
k8s_info
ADDITIONAL INFORMATION
Added
metadata_onlyoption ink8s_infomodule, enabling support for K8S API Metadata-only fetches.The
Acceptheader used whenmetadata_onlyoption is true also includes a fallback valueapplication/json;q=0.9as documented upstream, so that full objects are returned if the API doesn't support partial responses instead of an HTTP 406 error.Added integration tests to verify the behavior of the
metadata_onlyoption.Closes #1022