mirror of
https://github.com/kemko/nomad.git
synced 2026-01-09 11:55:42 +03:00
docs: remove reference to vSphere from CSI concepts docs (#16765)
The vSphere plugin is exclusive to k8s because it relies on k8s-APIs (and crashes without them being present). Upstream unfortunately will not support Nomad, so we shouldn't refer to it in our concept docs here.
This commit is contained in:
@@ -22,15 +22,14 @@ inside the plugin's tasks.
|
||||
|
||||
## CSI Plugins
|
||||
|
||||
Every storage vendor has its own APIs and workflows, and the
|
||||
industry-standard Container Storage Interface specification unifies
|
||||
these APIs in a way that's agnostic to both the storage vendor and the
|
||||
container orchestrator. Each storage provider can build its own CSI
|
||||
plugin. Jobs can claim storage volumes from AWS Elastic Block Storage
|
||||
(EBS) volumes, GCP persistent disks, Ceph, Portworx, vSphere, etc. The
|
||||
Nomad scheduler will be aware of volumes created by CSI plugins and
|
||||
schedule workloads based on the availability of volumes on a given
|
||||
Nomad client node.
|
||||
Every storage vendor has its own APIs and workflows, and the industry-standard
|
||||
Container Storage Interface specification unifies these APIs in a way that's
|
||||
agnostic to both the storage vendor and the container orchestrator. Each storage
|
||||
provider can build its own CSI plugin. Jobs can claim storage volumes from AWS
|
||||
Elastic Block Storage (EBS) volumes, GCP persistent disks, Ceph, Portworx,
|
||||
etc. The Nomad scheduler will be aware of volumes created by CSI plugins and
|
||||
schedule workloads based on the availability of volumes on a given Nomad client
|
||||
node.
|
||||
|
||||
A list of available CSI plugins can be found in the [Kubernetes CSI
|
||||
documentation][csi-drivers-list]. Spec-compliant plugins should work with Nomad.
|
||||
|
||||
Reference in New Issue
Block a user