a062782524
Automatic merge from submit-queue (batch tested with PRs 45508, 44258, 44126, 45441, 45320) cloud initialize node in external cloud controller @thockin This PR adds support in the `cloud-controller-manager` to initialize nodes (instead of kubelet, which did it previously) This also adds support in the kubelet to skip node cloud initialization when `--cloud-provider=external` Specifically, Kubelet 1. The kubelet has a new flag called `--provider-id` which uniquely identifies a node in an external DB 2. The kubelet sets a node taint - called "ExternalCloudProvider=true:NoSchedule" if cloudprovider == "external" Cloud-Controller-Manager 1. The cloud-controller-manager listens on "AddNode" events, and then processes nodes that starts with that above taint. It performs the cloud node initialization steps that were previously being done by the kubelet. 2. On addition of node, it figures out the zone, region, instance-type, removes the above taint and updates the node. 3. Then periodically queries the cloudprovider for node addresses (which was previously done by the kubelet) and updates the node if there are new addresses ```release-note NONE ``` |
||
|---|---|---|
| .. | ||
| src/k8s.io | ||
| copy.sh | ||
| godeps-json-updater.go | ||
| OWNERS | ||
| prime-apimachinery.sh | ||
| README.md | ||
This staging/src/k8s.io/client-go directory is the staging area of the client repo. It contains a versioned client, tools built around the client like the reflector, and all the client dependencies. The content will be periodically published to k8s.io/client-go repo.
The staged content is copied from the main repo, i.e., k8s.io/kubernetes, with directory rearrangement and necessary rewritings. To sync the content with the latest code in your local k8s.io/kubernetes, you need to run godep restore in k8s root directory, then run staging/copy.sh.
vendor/k8s.io/client-go is a symlink pointing to this staging area, so to use the packages in the staging area, you can import it as "vendor/client-go/", as if the client were vendored. The client will be vendored from k8s.io/client-go for real after the test matrix is converted to vendor k8s components.