Member-only story
Introduction
While you have multiple Kubernetes cluster and need a service mesh to manage all your services, this article will provide you an insight of the primary-remote istio cluster and how to deploy it. Kubernetes and Istio, together, will bring extensibility to your application, transparently and security to the traffic and achieve interoperability for multicluster.
Kubernetes
Kubernetes is a well-known container orchestrate platform, which can scale your containized application in seconds. And also provide user with load balancing, service discovery, etc.
You can say that Kubernetes is already a cluster with multiple nodes. It provide you with scalability. Why you need to build Istio on top of multi cluster?
Assuming that you have an application that is for internal use and you don’t want to expose it to the internet.
Assuming that you have an application runs with heavy load so you can’t affort it running in the same node pool as your web/mobile/db application because you are afraid of it will slow down them.
Assuming that you have an application that has a need to run in separate region and you want to failover in a smooth way.
There are many of examples.
Usually, if a client wants access to a Kubernetes services, it will send a request to ingress and then proxy to backend services by rules. And the requests will…
