This message was deleted.

Hi Ilan, thank you very much for your interest in s3gw. 1. By caching mechanism, do you mean a volatile memory cache to hold objects before they are flushed on volume? If this is the case, no it hasn't this feature. Can you explain us your idea of cache and your need for having that cache ? 2. Every s3gw can bind with a single volume, this is by design. You can scale in the sense that you can have how many s3gw installations you want on your k8s; but they all will be independent. What is your idea of scaling here?