You can specify a volume id, but then only have one replica. And, to
deploy, then you need downtime.
With a PVC and something smarter, you might be able to do some more cool
things.
But don't underestimate the power of simplicity, if it's enough for your
use case :-)
On Thursday, July 20, 2017,
+ Kubernetes dev, hope can get more comments/suggestions here.
Thanks,
Guangya
On Fri, Jul 21, 2017 at 8:42 AM, Guang Ya Liu wrote:
> Thanks Rodrigo!
>
> But even with deployment, I can still have volume mounts in the deployment
> to mount to external storage, so even using deployment, I can s
Thanks Rodrigo!
But even with deployment, I can still have volume mounts in the deployment
to mount to external storage, so even using deployment, I can still
have persistency,
right?
For statefulset, I can use volumeClaimTemplates to mount PVCs to have
persistency,
but how an it make upgrade eas
If you use redis without persistency, probably a deployment is fine.
Stateful sets are newer, and might help you (didn't look at the yaml) to
manage persistency in redis (and redis upgraded, etc.) More easily
On Wednesday, July 19, 2017, Guangya Liu wrote:
> Hi,
>
> I found that there are two w
Hi,
I found that there are two ways to deploy a Redis cluster, one is in
openshift, it is using
statefulset
https://github.com/openshift/origin/blob/master/examples/statefulsets/redis/redis.yaml
And another is in Kuberntes helm charts, it is using Deployment + Service
to deploy the Redis
clu
