Comments (10)
@nckturner App Mesh has supported tagging since we went GA, including tag-on-create; you're referring to AWS tagging right? Is that a path forward to address this?
from aws-app-mesh-controller-for-k8s.
We do have guidance on setting up multi EKS cluster with peered VPCs here and we have plans to launch support for a mesh across one VPC with multiple AWS accounts coming soon
from aws-app-mesh-controller-for-k8s.
Hello, any updates about multi-cluster support.
I would like reach a virtual services in the same mesh but different cluster.
Is that possible?
from aws-app-mesh-controller-for-k8s.
Since App Mesh doesn't support tagging yet (to my knowledge), we can add an "owner" field to the mesh custom resource, and only if it is set to true would be attempt to create or delete the mesh itself. Otherwise, we just look for it.
from aws-app-mesh-controller-for-k8s.
@efe-selcuk Yeah my mistake, we can use tags then as well. I think that's a better solution.
from aws-app-mesh-controller-for-k8s.
I have few clarifying questions that may help find the solution.
- In a multi-cluster mode, is each cluster using its own VPC or are they sharing same VPC?
- If they have individual VPCs then how is the connectivity established? (peering, transit-gw, privatelink,...)
- What is the service-discovery solution across cluster? Cloud Map HttpNamespace should work across VPC boundaries, and so does App Mesh EDS. However, registration of proper endpoints behind the service does not include enough metadata to support split-horizon discovery.
from aws-app-mesh-controller-for-k8s.
For my case:
1.- I have 2 EKS clusters in different VPC.
2.- I am not using peering, transit-gw.
3.- I did not know I needed another service to discover the services when I use APP Mesh. I supposed when I expose the virtualservice I could reach that service using that.
Please I would like to know what is the best way to connect my services, because all the documentation says for one cluster.
from aws-app-mesh-controller-for-k8s.
Thx for you support I did it using Cloudmap and so far so good
from aws-app-mesh-controller-for-k8s.
This is resolved in GA version.
It's possible to use two VPC with peered connection and using cloudmap as serviceDiscovery.
from aws-app-mesh-controller-for-k8s.
I am using the lates version of the controller (1.0.0) and when I have 2 clusters with 1 vpc and I deploy the mesh components to one cluster and then try to deploy the front end app to the other cluster, the mutating webhook denies the deployment as it cannot find a matching virtualnode, which is on the other cluster for it.
The previously mentioned blog post is what I followed, but that seems to be for the older controller. I am using CloudMap, but cant get that far as the controller wont even allow the deployment to deploy.
What am I missing?
from aws-app-mesh-controller-for-k8s.
Related Issues (20)
- Health check on /ready instead of /server_info
- Add support for configuring APPMESH_ENABLE_IPV6 env var in proxyinit container HOT 3
- Controller no longer respecting CloudMapDNS.ttl value when creating cloudmap services
- Support configuring envoy LISTENER_DRAIN_WAIT_TIME_S environment variable
- Setting appmesh.k8s.aws/sidecarEnv: "ENVOY_LOG_LEVEL=debug" does not change the pod env var HOT 3
- Documentation: Health Checks failing after tls.mode=STRICT
- Second Listener for Virtual Nodes HOT 2
- PostStart hook fails if `envoyAdminAccessPort` is set HOT 3
- GatewayRoute Selector Inconsistent Behavior
- Virtual Node DNS service discovery is not working as expected HOT 2
- Outdated Changelog and release list
- Support for GatewayRoute target port HOT 1
- Unable to create routes for VirtualRouter with multiple listener HOT 4
- GatewayRoute Admission Webhook not in keeping with AWS API/UI: match prefix does not need to end in '/' HOT 1
- After modyifing the virtualrouter/virtualnode k8s manifest file it not update changes inPlace HOT 11
- GrpcRouteMatch port match error despite defining it HOT 6
- can't inject env var with a comma in it's value HOT 4
- 🚨 appmesh-envoy:v1.27.0.0-prod does not run HOT 2
- Override APPMESH_EGRESS_IGNORED_PORTS in injected proxyInit container HOT 4
- Does the cloudmap namespace have to match the k8s namespace? HOT 10
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from aws-app-mesh-controller-for-k8s.