Repository navigation
node: provide or recommend a podresources API client #119817
Description
What would you like to be added?
The podresources API is a node-local API exposed by the kubelet graduating to GA in 1.28.
The project already exports the API definitition proper but not a client package.
Since this is a GA API, we should either provide easy to consume client code, or at least recommend a third party client.
For starters a golang client package is fine, and we should can extend and polish the existing client code.
Why is this needed?
Clients code wanting to consume the code maybe considering to reuse the existing client code, but this is actively discouraged.
One of the reasons seems to be that doing this will also require to import (and possibly vendor) k8s.io/kubernetes.
The only real option is to copy and paste the related code. For more details, the discussion started in the feature graduation blog post, which have more details and example code (the discussion should however continue here).
[edit] clarified why importing the existing client code is a bad idea, which if nothing else makes this issue more relevant. [/edit]
Activity
ffromani commentedon Aug 8, 2023
/sig node
k8s-ci-robot commentedon Aug 8, 2023
This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the
triage/acceptedlabel and provide further guidance.The
triage/acceptedlabel can be added by org members by writing/triage acceptedin a comment.Details
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
sftim commentedon Aug 8, 2023
How do we publish the
.protofiles for this? Are they a release artefact?How about making the sample API client code in another language (eg Python)? Using another language emphasizes that you can use this from a client implemented in any language.
We don't mind what language a third party writes their own implementation in, right?
ffromani commentedon Aug 8, 2023
Published in staging: https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/kubelet/pkg/apis/podresources/v1
That would be fine. I'm suggesting to promote the golang client because it's a reasonnable starting point and I know for sure there are golang projects consuming the API. But adding more clients is fine and helpful.
AFAIK we don't mind at all
k8s-triage-robot commentedon Jan 26, 2024
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
k8s-triage-robot commentedon Feb 25, 2024
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle rotten/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
k8s-triage-robot commentedon Mar 26, 2024
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/reopen/remove-lifecycle rottenPlease send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
k8s-ci-robot commentedon Mar 26, 2024
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Details
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
ffromani commentedon Mar 26, 2024
/reopen
k8s-ci-robot commentedon Mar 26, 2024
@ffromani: Reopened this issue.
Details
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
k8s-triage-robot commentedon Apr 25, 2024
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/reopen/remove-lifecycle rottenPlease send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
k8s-ci-robot commentedon Apr 25, 2024
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Details
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.