summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJędrzej Nowak <pigmej@gmail.com>2016-10-13 11:37:03 +0200
committerGitHub <noreply@github.com>2016-10-13 11:37:03 +0200
commit732eb5212b019930b4547495fab8b0a8a44f44d4 (patch)
tree738a045fb71632140d8248d3e812e27990cf1719
parentd15ea2f9b7dc4db51abe6c5f170f42dd614fa6c4 (diff)
Typos in contributing.md
-rw-r--r--sig-storage/contributing.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/sig-storage/contributing.md b/sig-storage/contributing.md
index 84b40fab..c22d9aff 100644
--- a/sig-storage/contributing.md
+++ b/sig-storage/contributing.md
@@ -31,7 +31,7 @@ A great way to get involved is to pick an issue and help address it. We would lo
For folks looking to add support for a new storage platform in Kubernetes, you have several options:
- Write an in-tree volume plugin or provisioner: You can contribute a new in-tree volume plugin or provisioner, that gets built and ships with Kubernetes, for use within the Persistent Volume Framework.
[See the Ceph RBD volume plugin example] (https://github.com/kubernetes/kubernetes/tree/master/pkg/volume/rbd) or [the AWS Provisioner example](https://github.com/kubernetes/kubernetes/pull/29006)
-- Write a FlexVolume plugin: This is an an out-of-tree volume plugin which you develop and build separately outside of Kubernetes.
+- Write a FlexVolume plugin: This is an out-of-tree volume plugin which you develop and build separately outside of Kubernetes.
You then install the plugin on every Kubernetes host within your cluster and then [configure the plugin in Kubernetes as a FlexVolume](https://github.com/kubernetes/kubernetes/tree/master/examples/volumes/flexvolume)
- Write a Provisioner Controller: You can write a separate controller that watches for pending claims with a specific selector label on them.
Once an appropriate claim is discovered, the controller then provisions the appropriate storage intended for the claim and creates a corresponding