Red Hat Bugzilla – Bug 1303361
[DOCS] [3.2] Document the restriction on targeting nodes for pod scheduling
Last modified: 2017-03-08 13:14 EST
In OSE 3.2, an administrator will not be able to schedule pods with a specific node in mind.
As of creating this bug the work on this feature is still underway, so check closer to the development whether this will make it in 3.2 and if it will impact OSE 3.2.
Dev for this feature is:
Abhishek Gupta, John Lamb
Trello card is:
QA for this feature is:
It might be sufficient to put this as a warning or note in the Admin Guide here but please make sure to cover a use case and consider if this may need to be mentioned in other guides.
PR created for this BZ:
I'll put this onto QA.
Deshuai Ma, please let me know if any information needs to be added to the PR. The trello card above has the process, which you have tested before. Thank you!
add comment to your pr
When this pr is merged, I will verify this bug.
Deshuai Ma, this is ready for another QA. Unfortunately, I can't merge this until it passes QA, so if you have any issues with the PR as it is now, please let me know. Then once it is verified then it can be merged:
(In reply to brice from comment #5)
> Deshuai Ma, this is ready for another QA. Unfortunately, I can't merge this
> until it passes QA, so if you have any issues with the PR as it is now,
> please let me know. Then once it is verified then it can be merged:
Add comment to the PR. thanks.
Commit pushed to master at https://github.com/openshift/openshift-docs
Merge pull request #1862 from bfallonf/2-bz1303361
Bug: 1303361 Added info on constraining pod placement
Verified to be in the 3.2 docs: