I have an application which runs on 1-2 nodes with multiple pods and an ingress controller. I need to deploy this application to multiple (say, 10+) locations over the world. Should I create a k8s cluster on every location or just use a large cluster? Also is there any way for an ingress controller …

[image] Jamesits: (say, 10+) locations over the world. Should I create a k8s cluster on every location or just use a large cluster? I would suggest avoiding one large stretched cluster. There are all sorts of issues that can crop up mostly around resource locality. Different networks at eac…

What environment are you running in? That makes a big difference in the network capabilities. I agree that stretching a cluster across DCs is a bad idea, unless ping time is single-digit ms (and even then, it introduces caveats).

Every node is a KVM virtual machine and I can have full control over the hypervisor and the network config. All nodes have public IPs and no firewall and it is possible to set up VPNs across the sites if needed (though it will be a pain to do this)

What UX do you want to expose to end-users? For example: Each site gets a public IP and DNS name. “ aaa.example.com ”, “ bbb.example.com ”, “ ccc.example.com ”. Traffic to “aaa” always goes to the US installation, and traffic to “bbb” always goes to EU. End users have to be region-aware. EU use…

It is an anycast DNS appliance, so it is by nature (3).

So, can you configure the ingress in each site to only route to bwckends in that site? Maybe I am missing something?

If the ingress is deployed manually it will be configured to route only to backends within the site; but for the k8s automatic ingress I’m not clear if it has the ability to differentiate backends of different sites. I think I should set up one k8s cluster on every node and use some multi-cluster c…

Maybe I misunderstand completely. Why would an ingress impl know anything about other sites unless you tell it? If you have one cluster per site, and one ingress impl per site, won’t that automatically do what you want?

This sounds like a case where you should avoid k8s almost entirely, and just pre-plan your deployment needs. How many different apps are you planning to put in each edge site? If the number is small (1-4) then k8s will mostly hurt you and add lots of overhead. You can always revise the plan later …

K8s deployment best practice for a multi-region application?

General Discussions

riking September 14, 2019, 9:05pm 13

In that case, a stretched cluster may be your best option? Or you could try out kubefed v2 and have 10 different single-master clusters.

I’m not very familiar with the solution space here, you might have to help build it!

Topic		Replies	Views
Should I use Kubernetes if my servers are geographically dispersed? General Discussions	8	2007	February 10, 2019
Kubernetes cluster spread over multiple regions General Discussions	0	386	October 12, 2024
Need advice for implementation k8s on-premise General Discussions	4	1010	December 3, 2021
Multi-region HA cluster with microk8s microk8s	2	2111	August 9, 2021
Multi-data center cluster General Discussions	1	3698	March 17, 2023

K8s deployment best practice for a multi-region application?

Related topics