-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Figure out multi namespace / multi control plane / mesh configuration #632
Comments
This is not a scale problem with dozens or event hundred of namespaces unless proven otherwise. It happens as a namespace is created. |
This should also be moved to pilot. |
There is relevant discussion in newly filled istio/old_pilot_repo#1272 but this issue is istio wide not only pilot related |
* Documented but unimplemented routes should return 501 not 404 * Re-order routes and name ruleid parameter Former-commit-id: 228338f654228b11060551f29cd6fb9f78aba6c6
* New ?codes= option to simulate HTTP errors from echo server * Don't change BUILD, it isn't needed * Restore BUILD
This is no longer an issue. |
it's only no longer an issue if we don't want to support multiple control planes in a cluster |
No concrete plans for multiple control planes, so let's re-open if/when needed, so we can focus on the ones we are working on. |
sgtm / agreed |
@andraxylia Could you please elaborate on the solution/conclusion/workaround/change_of_direction/etc? |
@msogrin we fixed the unnecessary config map copying part of the issue (the bug/perf/scale issue) and for now we are assuming istio watches all your namespaces in any given namespace |
* Support customized labels for istio-ingress Signed-off-by: Chun Lin Yang <clyang@cn.ibm.com> * update istio-egress
* Remove unnecessary env variables * update goldens
For 0.3 we need to solve the bootstrap configuration issue for the side cars
For testing (at least and also probably (tbd?) for production use cases) we want to support
multiple sets of multiple namespaces using 1 istio control plane and config in the same cluster
(and also multi cluster meshes eventually)
Right now the way the sidecar finds pilot and mixer is by assuming there is a mounted configmap coming from the namespace - that doesn't scale well with dozens of namespaces
See istio/old_pilot_repo#1153 and istio/old_pilot_repo#1154 for some 0.2 background
Note: even if we don't want to support multiple meshes in prod, the bootstrap can use streamlining and shouldn't require copying a configmap in each namespace (imo)
The text was updated successfully, but these errors were encountered: