kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #45683 from alculquicondor/nodename-warning 

Upgrade note about nodeName to warning
This commit is contained in:
Kubernetes Prow Robot 2024-03-26 21:02:52 -07:00 committed by GitHub
parent a2049966a9 0b15eccf6d
commit 801eefb4c2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
content/en/docs/concepts/scheduling-eviction/assign-pod-node.md
View File

@ -586,11 +586,12 @@ Some of the limitations of using `nodeName` to select nodes are:
for example OutOfmemory or OutOfcpu. for example OutOfmemory or OutOfcpu.
- Node names in cloud environments are not always predictable or stable. - Node names in cloud environments are not always predictable or stable.
{{< note >}} {{< warning >}}
`nodeName` is intended for use by custom schedulers or advanced use cases where `nodeName` is intended for use by custom schedulers or advanced use cases where
you need to bypass any configured schedulers. Bypassing the schedulers might lead to you need to bypass any configured schedulers. Bypassing the schedulers might lead to
failed Pods if the assigned Nodes get oversubscribed. You can use the [node affinity](#node-affinity) or the [`nodeselector` field](#nodeselector) to assign a Pod to a specific Node without bypassing the schedulers. failed Pods if the assigned Nodes get oversubscribed. You can use [node affinity](#node-affinity)
{{</ note >}} or the [`nodeSelector` field](#nodeselector) to assign a Pod to a specific Node without bypassing the schedulers.
{{</ warning >}}
Here is an example of a Pod spec using the `nodeName` field: Here is an example of a Pod spec using the `nodeName` field: