Using ConfigMaps when creating a Deployment from UI

[naisanza]

Issue details

I've figured out you can upload a ConfigMap.yaml and Dashboard will create a new ConfigMap for you. But when creating a new Deployment, there aren't any options or advanced options for selecting a ConfigMap to choose? Is there a way to select an added ConfigMap to the Deployment process in the UI?

Environment

Dashboard version: gcr.io/google_containers/kubernetes-dashboard-amd64:v1.5.1
Kubernetes Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"2016-12-14T00:57:05Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Kubernetes Server Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"2016-12-14T00:52:01Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Operating system: Linux k8s-master01 4.8.0-22-generic #24-Ubuntu SMP Sat Oct 8 09:15:00 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Node.js version:
Go version: 1.7.4

Steps to reproduce

1. Create ConfigMap.yaml
2. Upload ConfigMap.yaml via Dashboard +Create option
3. Create new Deployment
4. No option to select a ConfigMap, but there is an option to select a Secret

Observed result

No option to select a ConfigMap

Expected result

Option to select a ConfigMap (or documentation if you can use one of those other options to add as a ConfigMap, e.g. adding it as an environment variable, or keyword)

[bryk]

@IanLewis You started the thread about custom creation workflows for resources. Can you respond here?

[ianlewis]

Yah, I think supporting creation of objects is relatively low priority given the limited resources we have and user needs based on past surveys, but I'd like to track this as something interested folks could work on. See #1600 as the full tracking ticket.

[fejta-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta. /lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta. /lifecycle rotten /remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close