You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2018. It is now read-only.
Our Envoy solution pulls lots of tricks (iptables, init containers) that are either not applicable to some deployments or not supported by other proxies.
We should make sure that we can support nginx, linkerd, etc by leaving all the customizations as pluggable hooks that third-party contributors can fill in. Ideally, the choice of a proxy mesh should be an implementation detail to the rest of Istio.
The text was updated successfully, but these errors were encountered:
kyessenov
changed the title
Ensure that proxy injection + setup mechanism works for other proxies
[tracking] Ensure that proxy injection + setup mechanism works for other proxies
Jan 13, 2017
ayj
changed the title
[tracking] Ensure that proxy injection + setup mechanism works for other proxies
Ensure that proxy injection + setup mechanism works for other proxies
Jan 26, 2017
Use of features like SO_ORIG_DST is highly dependent on the proxy. And our transparent proxying relies on the proxy being able to distinguish upstream connections based on this feature. So, there is nothing much we can do about this. Besides, Linkerd folks have demonstrated that Pilot can be integrated with proxies other than Envoy.
Our Envoy solution pulls lots of tricks (iptables, init containers) that are either not applicable to some deployments or not supported by other proxies.
We should make sure that we can support nginx, linkerd, etc by leaving all the customizations as pluggable hooks that third-party contributors can fill in. Ideally, the choice of a proxy mesh should be an implementation detail to the rest of Istio.
The text was updated successfully, but these errors were encountered: