Madhusudan.C.S d9cea93eb6 [Federation] Do not build separate binaries for federation control plane components, hyperkube should be sufficient. ... Also build the hyperkube docker image on-the-fly. This is only a temporary fix until the proposal in issue https://github.com/kubernetes/kubernetes/issues/28630 is implemented. Also, the new build/deployment method completely obviates this step. We use debian image instead of busybox and do not build hyperkube as a static binary yet. Wait until PR https://github.com/kubernetes/kubernetes/pull/26028 is merged to build static hyperkube binaries.		2016-08-25 14:29:32 -07:00
..
.gitignore	Federation build and e2e test integration	2016-05-25 15:07:27 -07:00
federation-apiserver-cluster-service.yaml	Add federation controller manager to federation e2es	2016-06-02 00:17:11 -07:00
federation-apiserver-deployment.yaml	[Federation] Do not build separate binaries for federation control plane components, hyperkube should be sufficient.	2016-08-25 14:29:32 -07:00
federation-apiserver-lb-service.yaml	Federation build and e2e test integration	2016-05-25 15:07:27 -07:00
federation-apiserver-nodeport-service.yaml	Federation build and e2e test integration	2016-05-25 15:07:27 -07:00
federation-apiserver-secrets.yaml	Underscore is not a valid secret data key, so use underscore instead.	2016-08-25 00:12:12 -07:00
federation-controller-manager-deployment.yaml	[Federation] Do not build separate binaries for federation control plane components, hyperkube should be sufficient.	2016-08-25 14:29:32 -07:00
federation-etcd-pvc.yaml	Create a PD volume when deploying the federation with federation-up.	2016-06-29 22:01:50 -07:00
federation-ns.yaml	Federation build and e2e test integration	2016-05-25 15:07:27 -07:00