Home > Software design >  Kubernetes Cluster Federation retired?
Kubernetes Cluster Federation retired?

Time:12-29

I have come across a need that I need to serve application users based on their geo-location. One possibility, I could think of it to have application installed on multiple k8s clusters hosted in different region and then load-balance the traffic based on geo-location of the users.

While exploring this idea, I came across several articles on "Kubernetes Cluster Federation" (e.g. https://kubernetes.io/blog/2016/10/globally-distributed-services-kubernetes-cluster-federation/). But seems like this functionality has been retired as mentioned in https://github.com/kubernetes-retired/federation.

Does someone know:

  1. If there is any alternative for "Kubernetes Cluster Federation"?
  2. Is there any other solution/s to address the need of serving users based on their geo-location?
  3. If we leave the application part, is there any way to store the data in same geo-location?

Thanks!

CodePudding user response:

https://github.com/kubernetes-sigs/kubefed is a successor to the "Kubernetes Cluster Federation", though I am not sure what is its current state. If you want to deploy a global loadbalancer, I suggest to have a look into https://www.k8gb.io/ .

CodePudding user response:

...k8s clusters hosted in different region and then load-balance the traffic based on geo-location of the users

If you determine the user location simply by the network location, you can use DNS geolocation routing capability such as Route 53 to reach nearest services. In this context k8s federation is not required.

If we leave the application part, is there any way to store the data in same geo-location?

Apart from global scale database solution such as Aurora, Spanner, your application can point to a centralize database that resides in one of the region; if the increase latency is acceptable.

  • Related