emptyDir is the first in the list of volume types at
https://kubernetes.io/docs/concepts/storage/volumes/#emptydir. not sure
how i missed that! That will definitely work for me. I'm going to need to
do some investigation into behavior if local disk is exhausted, etc. This
is definitely a workable
On Thu, Mar 30, 2017 at 10:48 PM, Adam Schepis wrote:
>
> In my particular case the cache can be destroyed and rebuilt if a pod dies
> (either a new EBS, scrubbed EBS, etc)
So the hypothetical "inline claim" model might satisfy for you. I'm
asking these same questions of many people and getting
In my particular case the cache can be destroyed and rebuilt if a pod dies
(either a new EBS, scrubbed EBS, etc)
As it scales out to more pods and nodes, each would need their own space to
put cache. It would be great if they could share space on one big EBS
volume attached per node, but I wouldn'
You can't use PVClaim and Deployment together. You will get a single
claim to a single EBS volume. Unfortunately this is a weird
intersection of subsystems.
PVClaim says "This data has identity, and I will manage its lifetime",
and Deployment says "These pods have no identity, and you should
man
argh. hit post before i fixed the topic :\
On Friday, March 31, 2017 at 1:19:54 AM UTC-4, Adam Schepis wrote:
>
> I have a service that i would like to deploy on my cluster (on AWS). I am
> doing so with a Deployment. Each pod will require an available local disk
> cache for its purposes. I was
