Read-Only Persistent Volumes on vSAN File Services

This post was originally published on this site

I’m writing this post because of a misconception I had regarding how read-only volumes were configured in Kubernetes. I thought this was controlled by the accessModes parameter in the PersistentVolumeClaim manifest file. This is not the case. It is controlled from the Pod, which to me seems a bit strange. Why would this not be controlled from the PVC manifest? One of our engineers pointed me to a few Kubernetes discussions on the behaviour of accessModes and readOnly here and here. It would seem that I am not the only one confused by this behaviour. In this post, I deploy…

The post Read-Only Persistent Volumes on vSAN File Services appeared first on

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.