Bug 1302424 - [RFE] oc new-app option that sets nodeselector and serviceaccountname [NEEDINFO]
Summary: [RFE] oc new-app option that sets nodeselector and serviceaccountname
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-27 20:20 UTC by Ryan Howe
Modified: 2016-07-26 01:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-26 01:02:51 UTC
Target Upstream Version:
bparees: needinfo? (ccoleman)

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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?
Note You need to log in before you can comment on or make changes to this bug.