Skip to content
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

Receiving resources as Tables #6823

Open
arnozhai opened this issue Jan 24, 2025 · 4 comments
Open

Receiving resources as Tables #6823

arnozhai opened this issue Jan 24, 2025 · 4 comments
Labels
Waiting on feedback Issues that require feedback from User/Other community members

Comments

@arnozhai
Copy link

How do I use Kubernetes-client to query the pod list and receive resources in a table?

Image

@manusa
Copy link
Member

manusa commented Jan 24, 2025

Describe your use-case.
You can do this with a raw request, but it'd be better to know how exactly are you intending to use this.

@manusa manusa added the Waiting on feedback Issues that require feedback from User/Other community members label Jan 24, 2025
@arnozhai
Copy link
Author

Describe your use-case. You can do this with a raw request, but it'd be better to know how exactly are you intending to use this.

The size of a single pod is greater than 50 KB. I want to reduce the memory consumption when querying pod status .
Just likes execute kubectl get pod -A

@manusa
Copy link
Member

manusa commented Jan 24, 2025

The size of a single pod is greater than 50 KB. I want to reduce the memory consumption when querying pod status .
Just likes execute kubectl get pod -A

I assume you're talking about the size of the YAML descriptor for the Pod.

My understanding is that something like #5716 would also be of use.

@arnozhai
Copy link
Author

The size of a single pod is greater than 50 KB. I want to reduce the memory consumption when querying pod status .
Just likes execute kubectl get pod -A

I assume you're talking about the size of the YAML descriptor for the Pod.

My understanding is that something like #5716 would also be of use.

Yeap, the difference is that I expect it would return the resources with the metadata and staus, omitting spec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Waiting on feedback Issues that require feedback from User/Other community members
Projects
None yet
Development

No branches or pull requests

2 participants