You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 19, 2018. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?
The text was updated successfully, but these errors were encountered: