[zh] update assign-pod-node.md doc
This commit is contained in:
@@ -185,15 +185,13 @@ To make use of that label prefix for node isolation:
|
|||||||
前缀设置或修改标签。要使用该标签前缀进行节点隔离:
|
前缀设置或修改标签。要使用该标签前缀进行节点隔离:
|
||||||
|
|
||||||
<!--
|
<!--
|
||||||
1. Check that you're using Kubernetes v1.11+ so that NodeRestriction is available.
|
1. Ensure you are using the [Node authorizer](/docs/reference/access-authn-authz/node/) and have _enabled_ the [NodeRestriction admission plugin](/docs/reference/access-authn-authz/admission-controllers/#noderestriction).
|
||||||
2. Ensure you are using the [Node authorizer](/docs/reference/access-authn-authz/node/) and have _enabled_ the [NodeRestriction admission plugin](/docs/reference/access-authn-authz/admission-controllers/#noderestriction).
|
2. Add labels under the `node-restriction.kubernetes.io/` prefix to your Node objects, and use those labels in your node selectors.
|
||||||
3. Add labels under the `node-restriction.kubernetes.io/` prefix to your Node objects, and use those labels in your node selectors.
|
|
||||||
For example, `example.com.node-restriction.kubernetes.io/fips=true` or `example.com.node-restriction.kubernetes.io/pci-dss=true`.
|
For example, `example.com.node-restriction.kubernetes.io/fips=true` or `example.com.node-restriction.kubernetes.io/pci-dss=true`.
|
||||||
-->
|
-->
|
||||||
1. 检查是否在使用 Kubernetes v1.11+,以便 NodeRestriction 功能可用。
|
1. 确保你在使用[节点授权](/zh/docs/reference/access-authn-authz/node/)并且已经 _启用_
|
||||||
2. 确保你在使用[节点授权](/zh/docs/reference/access-authn-authz/node/)并且已经_启用_
|
|
||||||
[NodeRestriction 准入插件](/zh/docs/reference/access-authn-authz/admission-controllers/#noderestriction)。
|
[NodeRestriction 准入插件](/zh/docs/reference/access-authn-authz/admission-controllers/#noderestriction)。
|
||||||
3. 将 `node-restriction.kubernetes.io/` 前缀下的标签添加到 Node 对象,
|
2. 将 `node-restriction.kubernetes.io/` 前缀下的标签添加到 Node 对象,
|
||||||
然后在节点选择器中使用这些标签。
|
然后在节点选择器中使用这些标签。
|
||||||
例如,`example.com.node-restriction.kubernetes.io/fips=true` 或
|
例如,`example.com.node-restriction.kubernetes.io/fips=true` 或
|
||||||
`example.com.node-restriction.kubernetes.io/pci-dss=true`。
|
`example.com.node-restriction.kubernetes.io/pci-dss=true`。
|
||||||
@@ -216,7 +214,7 @@ feature, greatly expands the types of constraints you can express. The key enhan
|
|||||||
3. you can constrain against labels on other pods running on the node (or other topological domain),
|
3. you can constrain against labels on other pods running on the node (or other topological domain),
|
||||||
rather than against labels on the node itself, which allows rules about which pods can and cannot be co-located
|
rather than against labels on the node itself, which allows rules about which pods can and cannot be co-located
|
||||||
-->
|
-->
|
||||||
1. 语言更具表现力(不仅仅是“对完全匹配规则的 AND”)
|
1. 语言表达能力更强(不仅仅是“对完全匹配规则的 AND”)
|
||||||
2. 你可以发现规则是“软需求”/“偏好”,而不是硬性要求,因此,
|
2. 你可以发现规则是“软需求”/“偏好”,而不是硬性要求,因此,
|
||||||
如果调度器无法满足该要求,仍然调度该 Pod
|
如果调度器无法满足该要求,仍然调度该 Pod
|
||||||
3. 你可以使用节点上(或其他拓扑域中)的 Pod 的标签来约束,而不是使用
|
3. 你可以使用节点上(或其他拓扑域中)的 Pod 的标签来约束,而不是使用
|
||||||
@@ -369,7 +367,7 @@ in the [scheduler configuration](/docs/reference/scheduling/config/). For exampl
|
|||||||
例如:
|
例如:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
apiVersion: kubescheduler.config.k8s.io/v1beta1
|
apiVersion: kubescheduler.config.k8s.io/v1beta3
|
||||||
kind: KubeSchedulerConfiguration
|
kind: KubeSchedulerConfiguration
|
||||||
|
|
||||||
profiles:
|
profiles:
|
||||||
|
|||||||
Reference in New Issue
Block a user