diff options
| author | AdamDang <adam.dang@daocloud.io> | 2018-05-03 19:52:39 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-05-03 19:52:39 +0800 |
| commit | d33cd5c386b117b1ffb4f10799c807d1bd36ff55 (patch) | |
| tree | 04bf7b5206996fda8459c954fcefaa27d2d2513c | |
| parent | d8560d5f778e10e5e0641be2c0082547dcc950e5 (diff) | |
Typo fix: make is easy->make it easy/initilization->initiliazation
Fix two typos:
make is easy->make it easy
initilization->initiliazation
| -rw-r--r-- | keps/0002-controller-manager.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/keps/0002-controller-manager.md b/keps/0002-controller-manager.md index 1316b123..d1ff96af 100644 --- a/keps/0002-controller-manager.md +++ b/keps/0002-controller-manager.md @@ -50,7 +50,7 @@ replaces: ## Summary We want to remove any cloud provider specific logic from the kubernetes/kubernetes repo. We want to restructure the code -to make is easy for any cloud provider to extend the kubernetes core in a consistent manner for their cloud. New cloud +to make it easy for any cloud provider to extend the kubernetes core in a consistent manner for their cloud. New cloud providers should look at the [Creating a Custom Cluster from Scratch](https://kubernetes.io/docs/getting-started-guides/scratch/#cloud-provider) and the [cloud provider interface](https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/cloud.go#L31) which will need to be implemented. @@ -220,7 +220,7 @@ Kube-apiserver uses the cloud provider for two purposes Volumes need cloud providers, but they only need **specific** cloud providers. The majority of volume management logic resides in the controller manager. These controller loops need to be moved into the cloud-controller manager. The cloud -controller manager also needs a mechanism to read parameters for initilization from cloud config. This can be done via +controller manager also needs a mechanism to read parameters for initialization from cloud config. This can be done via config maps. There are two entirely different approach to refactoring volumes - |