<p>In Kubernetes deployments, you can specify volume mounts as readonly. Is there a performance advantage to it, or logical only?</p>

<p>Is it dependant on the volume type?</p>

<p>To make my intentions clear, I'm using a pv in a scenario where I have one writer and many readers, and noticed any fs operation on the mounted volume is much slower than on the volatile disk.</p>

Mugen
<p>It entirely depends on the volume type. Some might implement performance optimizations when they know the volume is read only.</p>
