Closed Manikkumar1988 closed 2 months ago
I believe having multiple Varnish instances sharing the same storage backend is not officially supported.^1
dont need to cache the same content which is available already on another replica of Varnish
For this scenario, I'd like to point you to the "Creating a self-routing Varnish cluster" guide from the official documentation. That deployment scenario can be implemented using this chart with the appropriate VCL configuration.
Signaller is trying to purge by fire and forget approach! Is there a way we can achieve the strong consistency for that?
Hi,
Currently is it possible to scale varnish horizontally(sharing same volume) for a single backend via -backend-service=backend-service that can have multiple replicas.
So dont need to cache the same content which is available already on another replica of Varnish
Or intention is to have only one replica of varnish for multiple replicas of the backend pod?