Skip to content
This repository has been archived by the owner on Jan 19, 2018. It is now read-only.

Figure out a way to support ConfigMap as a resource #204

Open
jberkus opened this issue Mar 28, 2016 · 1 comment
Open

Figure out a way to support ConfigMap as a resource #204

jberkus opened this issue Mar 28, 2016 · 1 comment

Comments

@jberkus
Copy link

jberkus commented Mar 28, 2016

Kubernetes' 1.2's ConfigMap is a fundamentally new resource type; the resources we're currently using to cover, say, volumes doesn't really work for it.

How should we extend the nulecule spec to cover it, especially since there's not an analog in other providers?

@goern
Copy link
Contributor

goern commented Jun 7, 2016

ConfigMaps are a way to provide run time configuration to Kubernetes based applications. A Nulecule implementation (eg Atomic App) could use it to provide configurations to Pods.

For example, the username/password required to deploy a database, in Nulecule universe that is a param of an application, could be translated to a ConfigMap by Atomic App, if Atomic App deployed to Kubernetes/OpenShift.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants