whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document that Device Plugin feature is Beta (1.10) (#7512)

Browse Source
This commit is contained in:
Qiming
2018-02-27 06:30:44 +05:30
committed by k8s-ci-robot
parent cf48480729
commit cdf1c13382
3 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/cluster-administration/device-plugins.md
+4 -3
View File
@@ -4,7 +4,7 @@ title: Device Plugins
description: Use the Kubernetes device plugin framework to implement plugins for GPUs, NICs, FPGAs, InfiniBand, and similar resources that require vendor-specific setup. description: Use the Kubernetes device plugin framework to implement plugins for GPUs, NICs, FPGAs, InfiniBand, and similar resources that require vendor-specific setup.
--- ---
{% include feature-state-alpha.md %} {% include feature-state-beta.md %}
{% capture overview %} {% capture overview %}
Starting in version 1.8, Kubernetes provides a Starting in version 1.8, Kubernetes provides a
@@ -20,8 +20,9 @@ that may require vendor specific initialization and setup.
## Device plugin registration ## Device plugin registration
The device plugins feature is gated by the `DevicePlugins` feature gate and is disabled by default. The device plugins feature is gated by the `DevicePlugins` feature gate which
When the device plugins feature is enabled, the kubelet exports a `Registration` gRPC service: is disabled by default before 1.10. When the device plugins feature is enabled,
the kubelet exports a `Registration` gRPC service:
```gRPC ```gRPC
service Registration { service Registration {
docs/reference/feature-gates.md
+2 -1
View File
@@ -42,7 +42,8 @@ different Kubernetes components.
| `CustomPodDNS` | `false` | Alpha | 1.9 | | | `CustomPodDNS` | `false` | Alpha | 1.9 | |
| `CustomResourceValidation` | `false` | Alpha | 1.8 | 1.8 | | `CustomResourceValidation` | `false` | Alpha | 1.8 | 1.8 |
| `CustomResourceValidation` | `true` | Beta | 1.9 | | | `CustomResourceValidation` | `true` | Beta | 1.9 | |
| `DevicePlugins` | `false` | Alpha | 1.8 | | | `DevicePlugins` | `false` | Alpha | 1.8 | 1.9 |
| `DevicePlugins` | `true` | Beta | 1.10 | |
| `DynamicKubeletConfig` | `false` | Alpha | 1.4 | | | `DynamicKubeletConfig` | `false` | Alpha | 1.4 | |
| `DynamicVolumeProvisioning` | `true` | Alpha | 1.3 | 1.7 | | `DynamicVolumeProvisioning` | `true` | Alpha | 1.3 | 1.7 |
| `DynamicVolumeProvisioning` | `true` | GA | 1.8 | | | `DynamicVolumeProvisioning` | `true` | GA | 1.8 | |
docs/tasks/manage-gpus/scheduling-gpus.md
+4 -3
View File
@@ -74,9 +74,10 @@ works on 1.8 and 1.9 as well. It will be deprecated in 1.10 and removed in
**From 1.8 onwards, the recommended way to consume GPUs is to use [device **From 1.8 onwards, the recommended way to consume GPUs is to use [device
plugins](/docs/concepts/cluster-administration/device-plugins).** plugins](/docs/concepts/cluster-administration/device-plugins).**
To enable GPU support through device plugins, a special **alpha** feature gate To enable GPU support through device plugins before 1,10, the `DevicePlugins`
`DevicePlugins` has to be set to true across the system: feature gate has to be explicitly set to true across the system:
`--feature-gates="DevicePlugins=true"`. `--feature-gates="DevicePlugins=true"`. This is no longer required starting
from 1.10.
Then you have to install NVIDIA drivers on the nodes and run an NVIDIA GPU device Then you have to install NVIDIA drivers on the nodes and run an NVIDIA GPU device
plugin ([see below](#deploying-nvidia-gpu-device-plugin)). plugin ([see below](#deploying-nvidia-gpu-device-plugin)).