-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Consider Exposing Pods in the Kubelet REST API #1934
Comments
We talked about this before. With the latest v1beta3 related change, kubelet now reads BoundPods from etcd instead of ContainerManifestList. So now we can expose pods in the kubelet API. But BoundPod doesn't have labels included. What are the usecases for pod's label? @bgrant0607 @smarterclayton |
BoundPod does have labels in v1beta3 |
It does but I specifically excluded it in the default conversion (to avoid leaking info until we decide to do it). ----- Original Message -----
|
Cool, I will expose API for cAdvisor to get pods on Node. Then labels later. |
Fixed it via #1964 |
For monitoring purposes it will be extremely useful to gather what pods are running on a node and those pod's labels. I believe that information is already available on the Kubelet. This issue is about exposing this information in the Kubelet's REST API.
cc @dchen1107
The text was updated successfully, but these errors were encountered: