whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove and redirect: getting-started/...cloud-controller. (#3853)

Browse Source
This commit is contained in:
Steve Perry
2017-05-19 11:42:31 -07:00
committed by GitHub
parent 10434a0484
commit d4cbd968fd
2 changed files with 3 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started-guides/running-cloud-controller.md
-9
View File
@@ -1,9 +0,0 @@
---
assignees:
- thockin
title: Building and Running cloud-controller-manager
---
{% include user-guide-content-moved.md %}
[Building and Running cloud-controller-manager](/docs/tasks/administer-cluster/running-cloud-controller/)
docs/tasks/administer-cluster/running-cloud-controller.md
+3
View File
@@ -2,6 +2,9 @@
assignees: assignees:
- thockin - thockin
title: Building and Running cloud-controller-manager title: Building and Running cloud-controller-manager
redirect_from:
- "/docs/getting-started-guides/running-cloud-controller/"
- "/docs/getting-started-guides/running-cloud-controller.html"
--- ---
Kubernetes version 1.6 contains a new binary called as `cloud-controller-manager`. `cloud-controller-manager` is a daemon that embeds cloud-specific control loops in Kubernetes. These cloud-specific control loops were originally in the kube-controller-manager. However, cloud providers move at a different pace and schedule compared to the Kubernetes project, and abstracting the provider-specific code to the `cloud-controller-manager` binary allows cloud provider vendors to evolve independently from the core Kubernetes code. Kubernetes version 1.6 contains a new binary called as `cloud-controller-manager`. `cloud-controller-manager` is a daemon that embeds cloud-specific control loops in Kubernetes. These cloud-specific control loops were originally in the kube-controller-manager. However, cloud providers move at a different pace and schedule compared to the Kubernetes project, and abstracting the provider-specific code to the `cloud-controller-manager` binary allows cloud provider vendors to evolve independently from the core Kubernetes code.