OpenShift Node Selector Operations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 28: | Line 28: | ||
=Configuring a Per-Project Node Selector= | =Configuring a Per-Project Node Selector= | ||
==When the Project is Created== | ==When the Project is Created== | ||
| Line 35: | Line 33: | ||
The [[OpenShift Concepts#Per-Project_Node_Selector|per-project 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' | [[OpenShift_Project_Operations#Per-Project_Node_Selector|oadm new-project]] ''<project-name>'' --node-selector='keyA=valueA,keyB=valueB' | ||
More details in: {{Internal| | More details in: {{Internal|OpenShift_Project_Operations#Per-Project_Node_Selector|OpenShift Project Operations}} | ||
==After the Project was Created== | ==After the Project was Created== | ||
| Line 52: | Line 50: | ||
{{Warn|Edit the "namespace", and not the "project", if attempting to edit the project you will get an error message saying that the field is immutable.}} | {{Warn|Edit the "namespace", and not the "project", if attempting to edit the project you will get an error message saying that the field is immutable.}} | ||
==External Resources== | |||
* https://docs.openshift.com/container-platform/3.5/admin_guide/managing_projects.html#setting-the-project-wide-node-selector | |||
=Configuring a Per-Pod Node Selector= | =Configuring a Per-Pod Node Selector= | ||
A [[OpenShift Concepts#Per-Pod_Node_Selector|per-pod node selector]] is generated when the pod is created, according to the rules specified here: | |||
{{Internal|OpenShift_Concepts#Per-Pod_Node_Selector|Per-Pod Node Selector}} | |||
==External Resources== | |||
* https://docs.openshift.com/container-platform/3.5/admin_guide/managing_projects.html#developer-specified-node-selectors | |||
Latest revision as of 23:00, 17 October 2017
Internal
Overview
Operations to manipulate node selectors.
Configuring a Cluster-Wide Default Node Selector
Sets up a cluster-wide default node selector:
- Edit the master configuration file /etc/origin/master/master-config.yaml and add or modify the value for the default node selector:
... projectConfig: defaultNodeSelector: "color=red,flavor=vanilla" ...
The master must be restarted to change to take effect:
External Resources
Configuring a Per-Project Node Selector
When the Project is Created
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'
More details in:
After the Project was Created
The node selector can be added after the project was created by editing the namespace metadata with oc edit:
oc edit namespace <my-project>
...
metadata:
annotations:
openshift.io/node-selector: "env=infra"
...
Edit the "namespace", and not the "project", if attempting to edit the project you will get an error message saying that the field is immutable.
External Resources
Configuring a Per-Pod Node Selector
A per-pod node selector is generated when the pod is created, according to the rules specified here: