From 07d3a89fada0de39799072dd6f9322cd967bc7a6 Mon Sep 17 00:00:00 2001 From: Matthew Wong Date: Thu, 16 Mar 2017 11:19:04 -0400 Subject: [PATCH] Add external provisioners to PV doc --- docs/user-guide/persistent-volumes/index.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/user-guide/persistent-volumes/index.md b/docs/user-guide/persistent-volumes/index.md index 4558b6fae5..63490f145f 100644 --- a/docs/user-guide/persistent-volumes/index.md +++ b/docs/user-guide/persistent-volumes/index.md @@ -356,6 +356,16 @@ parameters: Storage classes have a provisioner that determines what volume plugin is used 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 Storage classes have parameters that describe volumes belonging to the storage class. Different parameters may be accepted depending on the `provisioner`. For