OpenShift Project Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 26: | Line 26: | ||
In order to [[OpenShift_Node_Selector_Operations#Configuring_a_Per-Project_Node_Selector|set up a per-project node selector]], use: | In order to [[OpenShift_Node_Selector_Operations#Configuring_a_Per-Project_Node_Selector|set up a per-project node selector]], use: | ||
--node-selector='keyA=valueA,keyB=valueB' | oadm new-project --node-selector='keyA=valueA,keyB=valueB' | ||
While the "new-project" subcommand is available for both [[oadm]] and [[oc]], creating a new project with a node selector is only available with the oadm command. The new-project subcommand is not available to project developers when self-provisioning projects. | While the "new-project" subcommand is available for both [[oadm]] and [[oc]], creating a new project with a node selector is only available with the oadm command. The new-project subcommand is not available to project developers when self-provisioning projects. | ||
Revision as of 23:01, 17 October 2017
Internal
Overview
List All Projects
oc get projects
Describe a Project
oc describe project <project-name>
Create a new Project
oadm new-project
oc new-project
Per-Project Node Selector
In order to set up a per-project node selector, use:
oadm new-project --node-selector='keyA=valueA,keyB=valueB'
While the "new-project" subcommand is available for both oadm and oc, creating a new project with a node selector is only available with the oadm command. The new-project subcommand is not available to project developers when self-provisioning projects.