Open jberkus opened 8 years ago
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.
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?