Bug 1302424

Summary: [RFE] oc new-app option that sets nodeselector and serviceaccountname
Product: OpenShift Container Platform Reporter: Ryan Howe <rhowe>
Component: RFEAssignee: Dan McPherson <dmcphers>
Status: CLOSED WONTFIX QA Contact: Johnny Liu <jialiu>
Severity: low Docs Contact:
Priority: low    
Version: 3.1.0CC: aos-bugs, ccoleman, jokerman, mmccomas
Target Milestone: ---Flags: bparees: needinfo? (ccoleman)
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-26 01:02:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ryan Howe 2016-01-27 20:20:22 UTC 
Description of problem:
- Requesting the `oc new-app` to have option to use existing serviceaccount and also set nodeselector value for new-app


Version-Release number of selected component (if applicable):
v3.1.1.6


Additional info:

Example: 

oc new-app --docker-image=myregistry.com/mycompany/mysql --serviceaccount=example --nodeselector="zone=primary" 


The following would add a value for serviceaccountname under podspec and nodeselector under podspec for the deployment config.
Comment 1 Clayton Coleman 2016-02-07 19:41:49 UTC 
We will unlikely expose this on new-app, but we would like to expose this via the CLI.
Comment 2 Ben Parees 2016-07-25 19:38:18 UTC 
Clayton I think you're saying we'd like to have a "oc set nodeselector" and "oc set serviceaccount" command for editing deploymentconfigs, is that accurate?