question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ReadWriteMany unsupported for PVCs on GCP

See original GitHub issue

/kind bug

What steps did you take and what happened: When creating tfevent-pvc, it fails on GCP with this error: Failed to provision volume with StorageClass "standard": invalid AccessModes [ReadWriteMany]: only AccessModes [ReadWriteOnce ReadOnlyMany] are supported

What did you expect to happen: The PVC to be created without errors.

Anything else you would like to add: Since C2D doesn’t support v0.7.0 yet, this version (v1alpha2) should work on GCP without failures.

Environment:

  • Kubeflow version: v0.6.2 (latest in C2D)
  • Minikube version: n/a
  • Kubernetes version: (use kubectl version): client: v1.13.11, server: v1.12.10-gke.17
  • OS (e.g. from /etc/os-release): MacOS v10.14.6

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:17 (13 by maintainers)

github_iconTop GitHub Comments

2reactions
vpavlincommented, Dec 16, 2019

It is a common problem among cloud provider and storage backends in general. There are some heavily used (GCP PD, AWS EBS, Ceph) which do not support ReadWriteMany specifically because they won’t allow you to attach one block device to multiple nodes, thus if you scale up and scheduler distributes the load, containers won’t start because the volume will not be able to attach to multiple nodes.

Maybe it would make sense to note that in the example or Katib documentation that ReadWriteMany for storage backend is required (e.g. NFS), or think about a different option like using object storage somehow.

0reactions
barrys-smscommented, Nov 11, 2021

/reopen I’ve been working on a vSphere cluster and have noticed the same issue.

invalid AccessModes [ReadWriteMany]: only AccessModes [ReadWriteOnce] are supported

Using: kubernetes.io/vsphere-volume

Read more comments on GitHub >

github_iconTop Results From Across the Web

ReadWriteMany Persistent Volumes in Google Kubernetes ...
In this post I'm going to walk you through how to do that. Lets get started. Provision GCP Persistent Disk. gcloud compute disks...
Read more >
Persistent volumes and dynamic provisioning - Google Cloud
ReadWriteMany : The volume can be mounted as read-write by many nodes. PersistentVolume resources that are backed by Compute Engine persistent disks don't ......
Read more >
Persistent Volumes | Kubernetes
A PersistentVolumeClaim (PVC) is a request for storage by a user. It is similar to a Pod. Pods consume node resources and PVCs...
Read more >
kubernetes - How do I create a persistent volume claim with ...
Now we want to achieve the same thing on GKE/GCP where multiple pods interact with a file system ... GCE PD (ReadWriteMany is...
Read more >
Understanding persistent storage - OpenShift Documentation
Developers can use persistent volume claims (PVCs) to request PV resources without having specific knowledge of the underlying storage infrastructure.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found