Change:
}, { federation:           "union", <del> kubeconfigGlobal:     fakeKubeFiles[0], kubeconfigExplicit:   "", </del> <ins> kubeconfigGlobal:     fakeKubeFiles[1], kubeconfigExplicit:   fakeKubeFiles[2], </ins> dnsZoneName:          "example.test.", lbIP:                 lbIP, apiserverServiceType: v1.ServiceTypeLoadBalancer,

Discussion:
Is this a BUG REPORT or FEATURE REQUEST? (choose one): bug report Kubernetes version (use ): kubectl , kubefed, kubeadm binary version: compiled from master today kubectl version: # ./kubectl version Client Version: version.Info{Major:"", Minor:"", GitVersion:"v0.0.0-master+", GitCommit:"", GitTreeState:"not a git tree", BuildDate:"1970-01-01T00:00:00Z", GoVersion:"go1.8rc3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"6+", GitVersion:"v1.6.0-alpha.1", GitCommit:"", GitTreeState:"clean", BuildDate:"2017-01-31T02:31:32Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"} my cluster is bootstrapped by kubeadm Environment: Cloud provider or hardware configuration: hardware OS (e.g. from /etc/os-release): centOS 7.2 64bit Kernel (e.g. ): # uname -a Linux vmwarecgsl5.localdomain 3.10.0-327.22.2.el7.x8664 SMP Fri Nov 4 01:46:03 CST 2016 x8664 x8664 x8664 GNU/Linux Install tools: Others: What happened: when i ran , it exited with error message: error: context "brucetest" does not exist What you expected to happen: kubefed initialize a federation control plane successfully
cc
can u please run it (kubefed init) again with more verbose option (say --v=6) and then take the log. thanks!
the logs are very huge, so i pasted it here:
there seemed to be an issue in kubefed. You can please pull the commit in the PR I raised, if you want to verify and confirm before it gets merged. thanks!
after pulled your commit , the problem i mentioned above is gone. but the init process fall into an indefinite loop: I0215 23:45:03. 7427 ] GET https://:/healthz in 1 milliseconds I0215 23:45:03.

7427 ] Response Headers: I0215 23:45:05. 7427 ] curl -k -v -XGET -H "User-Agent: kubefed/v0.0.0 (linux/amd64) kubernetes/$Format" -H "Authorization: Basic YWRtaW46" -H "Accept: application/json, /" https://:/healthz I0215 23:45:05. 7427 ] GET https://:/healthz in 1 milliseconds I0215 23:45:05. 7427 ] Response Headers: I0215 23:45:07. 7427 ] curl -k -v -XGET -H "Authorization: Basic YWRtaW46" -H "Accept: application/json, /" -H "User-Agent: kubefed/v0.0.0 (linux/amd64) kubernetes/$Format" https://:/healthz I0215 23:45:07. 7427 ] GET https://:/healthz in 0 milliseconds I0215 23:45:07. 7427 ] Response Headers: I0215 23:45:09. 7427 ] curl -k -v -XGET -H "User-Agent: kubefed/v0.0.0 (linux/amd64) kubernetes/$Format" -H "Accept: application/json, /" -H "Authorization: Basic YWRtaW46" https://:/healthz I0215 23:45:09. 7427 ] GET https://:/healthz in 1 milliseconds I0215 23:45:09. 7427 ] Response Headers: I0215 23:45:11. 7427 ] curl -k -v -XGET -H "Accept: application/json, /" -H "User-Agent: kubefed/v0.0.0 (linux/amd64) kubernetes/$Format" -H "Authorization: Basic YWRtaW46" https://:/healthz I0215 23:45:11. 7427 ] GET https://:/healthz in 1 milliseconds I0215 23:45:11. 7427 ] Response Headers: I0215 23:45:13.

7427 ] curl -k -v -XGET -H "Accept: application/json, /" -H "User-Agent: kubefed/v0.0.0 (linux/amd64) kubernetes/$Format" -H "Authorization: Basic YWRtaW46" https://:/healthz I0215 23:45:13. 7427 ] GET https://:/healthz in 0 milliseconds ........ignored in there are some repeated errors i think maybe helpful: Feb 15 23:43:17 vmwarecgsl5.localdomain kubelet[2161]: I0215 23:43:17. 2161 ] checking backoff for container "controller-manager" in pod "brucetest-controller-manager--339xd" Feb 15 23:43:17 vmwarecgsl5.localdomain kubelet[2161]: I0215 23:43:17. 2161 ] Back-off 1m20s restarting failed container=controller-manager pod=brucetest-controller-manager--339xdfederation-system(-f394-11e6-9819-) Feb 15 23:43:17 vmwarecgsl5.localdomain kubelet[2161]: E0215 23:43:17. 2161 ] Error syncing pod -f394-11e6-9819-, skipping: failed to "StartContainer" for "controller-manager" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=controller-manager pod=brucetest-controller-manager--339xd_federation-system(-f394-11e6-9819-)" and should i file a new issue about this indefinite loop ?
Not necessary. It is already being tracked in PR to fix it is in