-
Notifications
You must be signed in to change notification settings - Fork 156
Support for metadata-only fetches in k8s_info module #1030
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Support for metadata-only fetches in k8s_info module #1030
Conversation
|
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 32s |
|
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 24s |
|
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 30s |
|
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 20s |
|
I pushed one last fix for linters (sorry for missing that, it didn't complain when I ran that locally), but failed sanity and integration test don't seem to be related with the changes in this PR, can you help me on this? |
|
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 32s |
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