To Storage or not to Storage

We are in Azure and using the Azure Files service for persistent storage. I posted our strategy here:

We tried using the GlusterFS/Convoy solution that was in the public catalog, but we found it was really sensitive to underlying system issues, and when it went down it would cause a cascade of stack/service failures. It just wasn’t ready for prime time.

In general in our rancher environments we avoid persistent storage for our applications. We run a couple of services like Redis and RabbitMQ which use the storage for persistence, but really do their work out of memory, so they don’t require really fast storage.

1 Like