sync device-plugins cluster-ip-allocation patch-releases
Update device-plugins.md Update patch-releases.mdpull/48583/head
parent
ead42dc157
commit
cefd6b347b
|
@ -904,6 +904,8 @@ Here are some examples of device plugin implementations:
|
|||
Intel GPU, FPGA, QAT, VPU, SGX, DSA, DLB and IAA devices
|
||||
* The [KubeVirt device plugins](https://github.com/kubevirt/kubernetes-device-plugins) for
|
||||
hardware-assisted virtualization
|
||||
* The [NVIDIA GPU device plugin](https://github.com/NVIDIA/k8s-device-plugin), NVIDIA's
|
||||
official device plugin to expose NVIDIA GPUs and monitor GPU health
|
||||
* The [NVIDIA GPU device plugin for Container-Optimized OS](https://github.com/GoogleCloudPlatform/container-engine-accelerators/tree/master/cmd/nvidia_gpu)
|
||||
* The [RDMA device plugin](https://github.com/hustcat/k8s-rdma-device-plugin)
|
||||
* The [SocketCAN device plugin](https://github.com/collabora/k8s-socketcan)
|
||||
|
@ -919,6 +921,7 @@ Here are some examples of device plugin implementations:
|
|||
* [Intel 设备插件](https://github.com/intel/intel-device-plugins-for-kubernetes)支持
|
||||
Intel GPU、FPGA、QAT、VPU、SGX、DSA、DLB 和 IAA 设备
|
||||
* [KubeVirt 设备插件](https://github.com/kubevirt/kubernetes-device-plugins)用于硬件辅助的虚拟化
|
||||
* [NVIDIA GPU 设备插件](https://github.com/NVIDIA/k8s-device-plugin)NVIDIA 的官方设备插件,用于公布 NVIDIA GPU 和监控 GPU 健康状态。
|
||||
* [为 Container-Optimized OS 所提供的 NVIDIA GPU 设备插件](https://github.com/GoogleCloudPlatform/container-engine-accelerators/tree/master/cmd/nvidia_gpu)
|
||||
* [RDMA 设备插件](https://github.com/hustcat/k8s-rdma-device-plugin)
|
||||
* [SocketCAN 设备插件](https://github.com/collabora/k8s-socketcan)
|
||||
|
|
|
@ -97,9 +97,9 @@ spec:
|
|||
type: ClusterIP
|
||||
```
|
||||
<!--
|
||||
but as it was explained before, the IP address 10.96.0.10 has not been reserved; if other Services are created
|
||||
before or in parallel with dynamic allocation, there is a chance they can allocate this IP, hence,
|
||||
you will not be able to create the DNS Service because it will fail with a conflict error.
|
||||
But, as it was explained before, the IP address 10.96.0.10 has not been reserved.
|
||||
If other Services are created before or in parallel with dynamic allocation, there is a chance they can allocate this IP.
|
||||
Hence, you will not be able to create the DNS Service because it will fail with a conflict error.
|
||||
-->
|
||||
但如前所述,IP 地址 10.96.0.10 尚未被保留。如果在 DNS 启动之前或同时采用动态分配机制创建其他 Service,
|
||||
则它们有可能被分配此 IP,因此,你将无法创建 DNS Service,因为它会因冲突错误而失败。
|
||||
|
|
|
@ -114,6 +114,8 @@ During the two-month maintenance mode period, Release Managers may cut
|
|||
additional maintenance releases to resolve:
|
||||
|
||||
- CVEs (under the advisement of the Security Response Committee)
|
||||
- [Vulnerabilities](/docs/reference/issues-security/official-cve-feed/) that have an assigned
|
||||
CVE ID (under the advisement of the Security Response Committee)
|
||||
- dependency issues (including base image updates)
|
||||
- critical core component issues
|
||||
|
||||
|
@ -127,6 +129,7 @@ dates for simplicity (every month has it).
|
|||
在两个月的维护模式期间,发布管理员可能会删减额外的维护版本以解决:
|
||||
|
||||
- CVE(在安全响应委员会的建议下)
|
||||
- 已分配 CVE ID 的[漏洞](/zh-cn/docs/reference/issues-security/official-cve-feed/)(在安全响应委员会的建议下)
|
||||
- 依赖问题(包括基础镜像更新)
|
||||
- 关键核心组件问题
|
||||
|
||||
|
|
Loading…
Reference in New Issue