Implementing Cluster Federation in Rancher with a Dedicated Environment

5th chunk of `content/en/blog/_posts/2016-07-00-Kubernetes-In-Rancher-Further-Evolution.md`

bbd491d78d8e3dfb52b1e257e9577deab93cf0425e9cbc9b00000001000003c2

![Screen Shot 2016-07-07 at 1.24.18 PM.png](https://lh6.googleusercontent.com/gmL0eoE2Z_m-KQbidAxrHA_gL8EDoflYuu_DKSxRiSm2RqTde-nYwGD65YBWzZWkCnbEG6NJ_NHCo0oHTP-PxNqWXt7k5Vp76JBOTNawsmlTeehOrPVY6nTZnEMl2ZH0V73_7f9E)





To support Cluster Federation via Kubernetes in Rancher, certain changes need to be done. Today each Kubernetes cluster is represented as a Rancher environment. In each Kubernetes environment, we create a full Kubernetes system stack comprised of several services: Kubernetes API server, Scheduler, Ingress controller, persistent etcd, Controller manager, Kubelet and Proxy (2 last ones run on every host). To setup Cluster Federation, we will create one extra environment where Cluster Federation stack is going to run:




 ![Screen Shot 2016-07-07 at 1.23.14 PM.png](https://lh6.googleusercontent.com/_76MDeSl_ac2AqN2lvEKgmvrFuV9Mtt9qHngsKKBAy-rcpdMcyo_UyNYdK2z5POoZwBGptVXUoX-11UDHD4axY8Lco15KydIwVd_PlLC0xJ2GZ_-4JN7bkP4pj8SY7mQ4JUXGIL6)

Title: Implementing Cluster Federation in Rancher with a Dedicated Environment

Summary

To enable Cluster Federation using Kubernetes in Rancher, modifications are needed. Currently, each Kubernetes cluster is a Rancher environment with a full Kubernetes system stack. To set up Cluster Federation, an additional environment will be created specifically for running the Cluster Federation stack.