Kubernetes EFS volumes mounted as RWO

0

Hi,

For a deployment that I need to do on Kubernetes, I have to define several different storage classes, one with RWO disk devices, and other one with RWM. As far as I am aware, EBS volumes are RWO, and EFS volumes are RWX, so the easy solution is to define a storage class for EBS volumes, and other one called for RWX on each type of drive. However, my concern is about EBS volumes. As far as I am aware, an EBS volume is attached to a single node, so the pod should be "tied" always to that node. If for whatever reason that node crash, the pod will not be able to arrange on a new node.

My question is: In order to avoid that problem, may I define a RWO volume also on EFS drivers (instead the default RWX type) ?

Andres
gefragt vor 8 Monaten506 Aufrufe
1 Antwort
0

if I understand the question correctly, yes you can set the access type of an EFS volume to RWO. See about halfway down this blog https://aws.amazon.com/blogs/storage/persistent-storage-for-kubernetes/

spec:
  accessModes:
    - ReadWriteOnce
profile picture
EXPERTE
Steve_M
beantwortet vor 8 Monaten
  • The problem is that access type is defined on the PVC, and not on the class.. And since this is a helm deployment, I can not change the access type used on the PVC. The helm install requires me to define a StorageClass in advance, and the PVC would use that StorageClass, but I can not change the spec of the PVC, is hard-coded on the helm. So, going in further details: It is possible to define the accessMode in the storageclass or I am forces to do it on the PVC ?

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen