OpenShift Node Selector Operations: Difference between revisions
Jump to navigation
Jump to search
Line 39: | Line 39: | ||
{{External|https://docs.openshift.com/container-platform/3.5/admin_guide/managing_projects.html#developer-specified-node-selectors}} | {{External|https://docs.openshift.com/container-platform/3.5/admin_guide/managing_projects.html#developer-specified-node-selectors}} | ||
Changes a [[OpenShift Concepts#Per-Pod_Node_Selector|per-pod node selector]]. |
Revision as of 04:50, 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'
More details in:
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.
Configuring a Per-Pod Node Selector
Changes a per-pod node selector.