-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Actuallize podresources description #24641
Actuallize podresources description #24641
Conversation
@AlexeyPerevalov: You must be a member of the kubernetes/website-milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Website milestone maintainers and have them propose you as an additional delegate for this responsibility. 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. |
Deploy preview for kubernetes-io-vnext-staging processing. Building with commit b61e575 https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5fab959b5a8ef10008f1d103 |
/milestone 1.20 |
/cc @annajung |
/sig architecture |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes sense to me. I haven't really checked the gRPC details though.
As this page is getting long, I wonder if it makes sense to move that gRPC service description within https://k8s.io/reference/ ?
(if you agree - we can do that move as a second PR against dev-1.20)
content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
Outdated
Show resolved
Hide resolved
|
||
```gRPC | ||
|
||
// WatchPodResourcesRequest is the request made to the Watch PodResourcesLister service |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PodResourcesLister
or PodResources
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. In both KEP (https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2043-pod-resource-concrete-assigments, https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/606-compute-device-assignment) PodResources was used, but in implementation PodResourcesLister is used now.
Documentation should be written according to implementation.
But what to do with KEP, rename it there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, feel free to update the KEP as well
I had the same think when edited. I thought it's reasonable to move PodResorcesLister section into new file. But what is it - https://k8s.io/reference/? Is it https://kubernetes.io/docs/reference/? |
0317f94
to
3de9794
Compare
/cc @dashpole |
/remove-sig architecture |
Not only PR 93243, but also in this PR was mentioned API from kubernetes/kubernetes#95734. |
/hold |
3de9794
to
edb0eb8
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @reylejano-rxm |
Would you have a chance to rebase this against dev-1.20? It's currently got a merge conflict. |
@@ -204,7 +259,7 @@ DaemonSet, `/var/lib/kubelet/pod-resources` must be mounted as a | |||
{{< glossary_tooltip term_id="volume" >}} in the plugin's | |||
[PodSpec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core). | |||
|
|||
Support for the "PodResources service" requires `KubeletPodResources` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to be enabled. It is enabled by default starting with Kubernetes 1.15. | |||
Support for the "PodResourcesLister service" requires `KubeletPodResources` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to be enabled. It is enabled by default starting with Kubernetes 1.15. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: You can remove the double quotes around, PodResourceLister service ...
and possibly format the name of the service with single back quotes,
PodResourcesLister
?
@@ -193,9 +193,64 @@ for these devices: | |||
// node resources consumed by pods and containers on the node | |||
service PodResourcesLister { | |||
rpc List(ListPodResourcesRequest) returns (ListPodResourcesResponse) {} | |||
rpc GetAllocatableResources(AllocatableResourcesRequest) returns (AllocatableResourcesResponse) {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an API offered by the kubelet? gRPC only?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes.
/retest |
This commit updates description according to kubernetes/enhancements#1884 Signed-off-by: Alexey Perevalov <alexey.perevalov@huawei.com>
…/device-plugins.md Co-authored-by: Tim Bannister <tim@scalefactory.com>
…/device-plugins.md Co-authored-by: Tim Bannister <tim@scalefactory.com>
e2f6f69
to
b61e575
Compare
/hold cancel |
/hold |
Hi @AlexeyPerevalov Since the code freeze is on effect, wondering if folks raise exception for this since one of the PR is not merged yet |
Note: Exception filed (pending approval) |
/hold |
Exception request has been denied for this enhancement. /milestone clear |
@annajung: Closed this PR. 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. |
This commit updates description according to
kubernetes/enhancements#1884
/milestone 1.20
Issue: kubernetes/enhancements#2043
Signed-off-by: Alexey Perevalov alexey.perevalov@huawei.com