Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upgrade note about nodeName to warning #45683

Merged
merged 1 commit into from Mar 27, 2024
Merged

Upgrade note about nodeName to warning #45683

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 4 additions & 3 deletions content/en/docs/concepts/scheduling-eviction/assign-pod-node.md
View file
Open in desktop
Expand Up @@ -586,11 +586,12 @@ Some of the limitations of using `nodeName` to select nodes are:
for example OutOfmemory or OutOfcpu.
- 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
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.
{{</ note >}}
failed Pods if the assigned Nodes get oversubscribed. You can use [node affinity](#node-affinity)
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:

Expand Down