Clean up page device-plugins
parent
c475d558e0
commit
d08ae655fd
|
@ -297,7 +297,6 @@ However, calling `GetAllocatableResources` endpoint is not sufficient in case of
|
||||||
update and Kubelet needs to be restarted to reflect the correct resource capacity and allocatable.
|
update and Kubelet needs to be restarted to reflect the correct resource capacity and allocatable.
|
||||||
{{< /note >}}
|
{{< /note >}}
|
||||||
|
|
||||||
|
|
||||||
```gRPC
|
```gRPC
|
||||||
// AllocatableResourcesResponses contains informations about all the devices known by the kubelet
|
// AllocatableResourcesResponses contains informations about all the devices known by the kubelet
|
||||||
message AllocatableResourcesResponse {
|
message AllocatableResourcesResponse {
|
||||||
|
@ -396,4 +395,3 @@ Here are some examples of device plugin implementations:
|
||||||
* Learn about the [Topology Manager](/docs/tasks/administer-cluster/topology-manager/)
|
* Learn about the [Topology Manager](/docs/tasks/administer-cluster/topology-manager/)
|
||||||
* Read about using [hardware acceleration for TLS ingress](/blog/2019/04/24/hardware-accelerated-ssl/tls-termination-in-ingress-controllers-using-kubernetes-device-plugins-and-runtimeclass/)
|
* Read about using [hardware acceleration for TLS ingress](/blog/2019/04/24/hardware-accelerated-ssl/tls-termination-in-ingress-controllers-using-kubernetes-device-plugins-and-runtimeclass/)
|
||||||
with Kubernetes
|
with Kubernetes
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue