-
Notifications
You must be signed in to change notification settings - Fork 40k
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.
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
Update API comment for nodeName to match system behavior #124062
Update API comment for nodeName to match system behavior #124062
Conversation
/label api-review |
/assign @liggitt |
// requirements. | ||
// NodeName indicates in which node this pod is scheduled. | ||
// If empty, this pod is a candidate for scheduling by the scheduler defined in schedulerName. | ||
// If it is non-empty, the kubelet for this node becomes responsible for the lifecycle of this pod. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we could also mention using nodeSelector and affinity.nodeAffinity to target specific nodes while still allowing scheduling to work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could I just link to the website documentation instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A link out is fine, but some indication this is the wrong field to use if you want scheduling involved seems important
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added
Change-Id: I039b441f4525d280b1ea693d782fe0f43794d9f7
8db69c9
to
1a2dba4
Compare
/triage accepted |
/retest |
/lgtm |
LGTM label has been added. Git tree hash: 3d60275c75e6d9fc93d68b9d1b57c5f83f5699fa
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
In light of kubernetes/enhancements#3521 (comment), updating API documentation to reflect the system behavior.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: