OpenShift Node Selector Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
{{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}} | ||
==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: | The [[OpenShift Concepts#Per-Project_Node_Selector|per-project node selector]] can be set up when the project is created: | ||
| Line 22: | Line 24: | ||
More details in: {{Internal|oadm new-project|oadm new-project}} | More details in: {{Internal|oadm new-project|oadm new-project}} | ||
==After the Project was Created== | |||
The node selector can be added after the project was created by editing the namespace metadata with [[oc edit]]: | The node selector can be added after the project was created by editing the namespace metadata with [[oc edit]]: | ||
Revision as of 19:13, 30 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
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.
Configuring a Per-Pod Node Selector
A per-pod node selector can only be assigned when the pod is created:
apiVersion: v1
kind: Pod
spec:
nodeSelector:
keyA: valueA
...
Once the pod has been created, the value becomes immutable and an attempt to change it will fail. For more details on pod state see Pods.