OpenShift Node Selector Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
{{External|https://docs.openshift.com/container-platform/3.5/admin_guide/managing_projects.html#setting-the-project-wide-node-selector}} | {{External|https://docs.openshift.com/container-platform/3.5/admin_guide/managing_projects.html#setting-the-project-wide-node-selector}} | ||
The node selector can be set up when the project is created: | The [[OpenShift Concepts#Per-Project_Node_Selector|per-project node selector]] can be set up when the project is created: | ||
oadm new-project ''<project-name>'' --node-selector='keyA=valueA,keyB=valueB' | oadm new-project ''<project-name>'' --node-selector='keyA=valueA,keyB=valueB' | ||
=Configuring a Per-Pod Node Selector= | |||
The [[OpenShift Concepts#Per-Pod_Node_Selector|per-pod node selector]]. | |||
Revision as of 04:01, 6 July 2017
Internal
Overview
Operations to manipulate node selectors.
Configuring a Cluster-Wide Default Node Selector
Sets up a cluster-wide default node selector.
Configuring a Per-Project Node Selector
The per-project node selector can be set up when the project is created:
oadm new-project <project-name> --node-selector='keyA=valueA,keyB=valueB'