<p dir="auto">For cases where a small amount of static data is desired. This could include</p>
<ol dir="auto">
<li>configuration for containers whose process is configured by files</li>
<li>small-medium amounts of static data, such as an archive of www data for a static site server</li>
<li>inputs to a process that has a small input to work ratio</li>
</ol>
<p dir="auto">Example use cases:</p>
<ul dir="auto">
<li>allow developers to specify data along side the pod it's used with, instead of needing to put it "somewhere else" (EBS / PD / RBD)</li>
<li>allow Kubernetes-native process coordinators to pass input data to worker pods</li>
</ul>
<p dir="auto">For developers, this would be facilitated by a kubectl plugin (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="105000432" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/13606" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/13606/hovercard" href="https://github.com/kubernetes/kubernetes/issues/13606">#13606</a>) in a similar way to what is proposed for easing secret creation (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="58949840" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/4822" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/4822/hovercard" href="https://github.com/kubernetes/kubernetes/issues/4822">#4822</a>). The plugin would handle archive creation and encoding for inclusion in the manifest.</p>
<p dir="auto">The size of this data would be limited, as it would be living in etcd. I don't know what a reasonable limit is as I'm not familiar enough with etcd. I would assume a couple hundred KB at the most?</p>
<p dir="auto">This would map closely to Docker's native volumes support, and allow people to build and version pre-baked data as containers.  Maybe read-only?  Haven't thought that far...</p>