OiO.lk Community platform!

Oio.lk is an excellent forum for developers, providing a wide range of resources, discussions, and support for those in the developer community. Join oio.lk today to connect with like-minded professionals, share insights, and stay updated on the latest trends and technologies in the development field.
  You need to log in or register to access the solved answers to this problem.
  • You have reached the maximum number of guest views allowed
  • Please register below to remove this limitation

Multiple Istio Mesh in single EKS cluster

  • Thread starter Thread starter Suvendu Mandal
  • Start date Start date
S

Suvendu Mandal

Guest
We are running an Istio mesh in one single EKS cluster. The setup looks like this:

  1. One Istio Control Plane
  2. One Mesh
  3. Two Applications Namespaces (K8s)

Due to different business workload, I am thinking of creating another mesh in the same cluster. The setup will look like this:

  1. Two Control Planes
  2. Two Meshes
  3. Four Application Namespaces - 2 per Mesh

I was looking at the Isito Deployment Models https://istio.io/latest/docs/ops/deployment/deployment-models/

From the documentation, it is not clear that, whether two control planes are required for two meshes in one single cluster.

Got a hold of this document: https://istio.io/latest/docs/setup/install/multiple-controlplanes/ This gave an example of two control planes for two meshes but I am not sure whether it can be implemented in production or not.

Questions:

  1. Do I need to create two Istio control planes for two meshes in one single cluster? Is there any problems or implementation issues with this deployment pattern?
  2. Is there any example or documentation which explains one Istio control plane with two meshes in one single cluster deployment method?
  3. Can we deploy the above example in production? Two Istio control planes with two meshes in one single EKS cluster.

Thanks, Suvendu
<p>We are running an Istio mesh in one single EKS cluster.
The setup looks like this:</p>
<ol>
<li>One Istio Control Plane</li>
<li>One Mesh</li>
<li>Two Applications Namespaces (K8s)</li>
</ol>
<p>Due to different business workload, I am thinking of creating another mesh in the same cluster.
The setup will look like this:</p>
<ol>
<li>Two Control Planes</li>
<li>Two Meshes</li>
<li>Four Application Namespaces - 2 per Mesh</li>
</ol>
<p>I was looking at the Isito Deployment Models <a href="https://istio.io/latest/docs/ops/deployment/deployment-models/" rel="nofollow noreferrer">https://istio.io/latest/docs/ops/deployment/deployment-models/</a></p>
<p>From the documentation, it is not clear that, whether two control planes are required for two meshes in one single cluster.</p>
<p>Got a hold of this document: <a href="https://istio.io/latest/docs/setup/install/multiple-controlplanes/" rel="nofollow noreferrer">https://istio.io/latest/docs/setup/install/multiple-controlplanes/</a>
This gave an example of two control planes for two meshes but I am not sure whether it can be implemented in production or not.</p>
<p>Questions:</p>
<ol>
<li>Do I need to create two Istio control planes for two meshes in one single cluster? Is there any problems or implementation issues with this deployment pattern?</li>
<li>Is there any example or documentation which explains one Istio control plane with two meshes in one single cluster deployment method?</li>
<li>Can we deploy the above example in production? Two Istio control planes with two meshes in one single EKS cluster.</li>
</ol>
<p>Thanks,
Suvendu</p>
Continue reading...
 

Latest posts

Online statistics

Members online
0
Guests online
1
Total visitors
1
Ads by Eonads
Top