Comments (3)
We have an upcoming use case where our workloads would go under multiple private networks where within each network services could be both mesh-aware and external to the mesh. We plan registering the external to mesh services as external service with the zone binding as this way mesh knows exactly which zone egress can access the specific "private" service.
Ideally we would like to be able to bind external service to multiple zones as there can be a scenario where multiple mesh zones are placed within a network and only few can access specific endpoint, being able to reference multiple zones makes a better case for HA in case one zone goes dark.
If binding the external service to zone feature is removed from future release of Kuma we won't be able to use Kuma much longer when the described use case becomes a majority of our workload placement use cases.
from kuma.
triage: this would probably be done by defining MeshExternalService in that zone
from kuma.
@slonka Why are we willing to define resources at the zone level? We have GlobalCP. So, why can't we simply create the resource in the GlobalCP and let it decide the ZoneCPs it needs the resources to be forwarded?
from kuma.
Related Issues (20)
- AutoReachable services with MeshExternalService
- Design `from` policies with `spec.targetRef` selecting whole proxies
- Route MeshExternalService traffic through egress only
- Add tests for API server errors
- unknown namespace for the cache error while working with some namespaces HOT 3
- Dataplane fails to run if Envoy version is mismatched HOT 3
- Kuma depends on EOL Envoy HOT 1
- Support for ServiceMap with Deligated GW HOT 3
- Loosing leader election leading to a restart that causes CI failure HOT 2
- Add support for new `MeshService` in `spec.to[].targetRef` in MeshTCPRoute/MeshHTTPRoute policy HOT 1
- MeshAccessLog should be able to configure for MeshExternalService
- HTTP/1.1 Header casing HOT 2
- Watchdog waits an entire period before first tick HOT 1
- Deprecate yes/no values for boolean annotations HOT 1
- allow MeshHTTPRoute with backendRef having appProtocol set to tcp HOT 1
- Support TLS connections between gateways and backends HOT 1
- Add E2E test for application probes proxy and virtual probes HOT 1
- keep CP running and strive for next leader once leader election lost HOT 3
- `kuma.io/mesh` does not work as labels of namespaces or pods HOT 1
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 kuma.