Add external provisioners to PV doc
parent
d4383a4b6a
commit
07d3a89fad
|
@ -356,6 +356,16 @@ parameters:
|
||||||
Storage classes have a provisioner that determines what volume plugin is used
|
Storage classes have a provisioner that determines what volume plugin is used
|
||||||
for provisioning PVs. This field must be specified.
|
for provisioning PVs. This field must be specified.
|
||||||
|
|
||||||
|
You are not restricted to specifying the "internal" provisioners
|
||||||
|
listed here (whose names are prefixed with "kubernetes.io" and shipped
|
||||||
|
alongside Kubernetes). You can also run and specify external provisioners,
|
||||||
|
which are independent programs that follow a [specification](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/volume-provisioning.md)
|
||||||
|
defined by Kubernetes. Authors of external provisioners have full discretion
|
||||||
|
over where their code lives, how the provisioner is shipped, how it needs to be
|
||||||
|
run, what volume plugin it uses (including Flex), etc. The repository [kubernetes-incubator/external-storage](https://github.com/kubernetes-incubator/external-storage)
|
||||||
|
houses a library for writing external provisioners that implements the bulk of
|
||||||
|
the specification plus various community-maintained external provisioners.
|
||||||
|
|
||||||
### Parameters
|
### Parameters
|
||||||
Storage classes have parameters that describe volumes belonging to the storage
|
Storage classes have parameters that describe volumes belonging to the storage
|
||||||
class. Different parameters may be accepted depending on the `provisioner`. For
|
class. Different parameters may be accepted depending on the `provisioner`. For
|
||||||
|
|
Loading…
Reference in New Issue