Manage AWS Mesh resource per EKS cluster

[int128]

Is your feature request related to a problem?
We upgrade an EKS cluster by blue-green strategy as follows:

1. Create a new EKS cluster and deploy our applications
2. Switch the traffic to the new cluster
3. Delete the old EKS cluster

During the migration, both old and new clusters are running.
We deploy same manifests to both clusters.
Consequently, both cluster manage the same AWS Mesh resource.
It would be nice if we can manage an AWS Mesh resource per an EKS cluster.

Describe the solution you'd like
It would be nice if we can set a prefix to an AWS Mesh name by the controller.
For example,

• Set a prefix of Mesh in the controller config (we can set it by the Helm values)
• Add an option to acquire the cluster name from EKS API
• Add a custom resource of config for meshes, such as MeshConfig

I think the first option is simple. How do you think?

Thanks.

[BrokenKage]

I have the same use case where I have a blue/green clusters which are spun up and down when needed.
Instead of a prefix I suggest being able to use an existing AppMesh?