From 59503364756a9e33ca5793c0813c2868bf584e1e Mon Sep 17 00:00:00 2001 From: Ashley Schuett Date: Wed, 28 Nov 2018 16:56:45 -0500 Subject: [PATCH] update link to CloudProvider Interface (#11228) --- content/en/docs/concepts/architecture/cloud-controller.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/architecture/cloud-controller.md b/content/en/docs/concepts/architecture/cloud-controller.md index de79d9d52c..82f791ff1f 100644 --- a/content/en/docs/concepts/architecture/cloud-controller.md +++ b/content/en/docs/concepts/architecture/cloud-controller.md @@ -109,7 +109,7 @@ The PersistentVolumeLabels controller moves the cloud-dependent functionality of ## Plugin mechanism -The cloud controller manager uses Go interfaces to allow implementations from any cloud to be plugged in. Specifically, it uses the CloudProvider Interface defined [here](https://github.com/kubernetes/kubernetes/tree/master/pkg/cloudprovider). +The cloud controller manager uses Go interfaces to allow implementations from any cloud to be plugged in. Specifically, it uses the CloudProvider Interface defined [here](https://github.com/kubernetes/cloud-provider/blob/9b77dc1c384685cb732b3025ed5689dd597a5971/cloud.go#L42-L62). The implementation of the four shared controllers highlighted above, and some scaffolding along with the shared cloudprovider interface, will stay in the Kubernetes core. Implementations specific to cloud providers will be built outside of the core and implement interfaces defined in the core.