summaryrefslogtreecommitdiff
path: root/keps
diff options
context:
space:
mode:
authorCheng Pan <chengpan@amazon.com>2018-11-29 06:28:17 +0000
committerCheng Pan <chengpan@amazon.com>2018-11-29 06:28:17 +0000
commitf13bd2428bfee4e5a265793899741a9ce09c3e0f (patch)
tree321de2a2479d7d78e85125566113df61936c95a8 /keps
parentf9b13c3f121d566b8db00846f5a89c6c694b98ad (diff)
Fix misspell
Diffstat (limited to 'keps')
-rw-r--r--keps/sig-aws/0034-20181127-aws-ebs-csi-driver.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/keps/sig-aws/0034-20181127-aws-ebs-csi-driver.md b/keps/sig-aws/0034-20181127-aws-ebs-csi-driver.md
index eda85e5b..74d349c7 100644
--- a/keps/sig-aws/0034-20181127-aws-ebs-csi-driver.md
+++ b/keps/sig-aws/0034-20181127-aws-ebs-csi-driver.md
@@ -34,7 +34,7 @@ status: provisional
* [Implementation History](#implementation-history)
## Summary
-AWS EBS CSI Driver implements [Container Storage Interface](https://github.com/container-storage-interface/spec/tree/master) which is the standard of storage interface for container. It provides the same in-tree AWS EBS plugin features including volume creation, volume attachment, volume mounting and volume scheduling. It is also configurable on what is the EBS volume type to create, what is the file system file should be formatted, which KMS key to use to create encrpyted volume, etc.
+AWS EBS CSI Driver implements [Container Storage Interface](https://github.com/container-storage-interface/spec/tree/master) which is the standard of storage interface for container. It provides the same in-tree AWS EBS plugin features including volume creation, volume attachment, volume mounting and volume scheduling. It is also configurable on what is the EBS volume type to create, what is the file system file should be formatted, which KMS key to use to create encrypted volume, etc.
## Motivation
Similar to CNI plugins, AWS EBS CSI driver will be a stand alone plugin that lives out-of-tree of kuberenetes. Being out-of-tree, it will be benefit from being modularized, maintained and optimized without affecting kubernetes core code base. Aside from those benefits, it could also be consumed by other container orchestrators such as ECS.