You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/zh-cn/docs/concepts/scheduling-eviction/assign-pod-node.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -815,6 +815,18 @@ Some of the limitations of using `nodeName` to select nodes are:
815
815
而其失败原因中会给出是否因为内存或 CPU 不足而造成无法运行。
816
816
- 在云环境中的节点名称并不总是可预测的,也不总是稳定的。
817
817
818
+
{{< note >}}
819
+
<!--
820
+
`nodeName`is intended for use by custom schedulers or advanced use cases where
821
+
you need to bypass any configured schedulers. Bypassing the schedulers might lead to
822
+
failed Pods if the assigned Nodes get oversubscribed. You can use [node affinity](#node-affinity) or a the [`nodeselector` field](#nodeselector) to assign a Pod to a specific Node without bypassing the schedulers.
0 commit comments