-
Notifications
You must be signed in to change notification settings - Fork 91
Implement Ingress Controller for Envoy #6
Comments
That sounds like a good target. I would add that Manager needs to support a regular proxy config, in addition to Istio Proxy, to fully reproduce an ingress controller. There is a difference in proxy topology for the edge proxy. |
@louiscryan @kyessenov trying to flesh out the scope, please weigh in so we're on the same page. This is my understanding of the task, as worded: Since this issue was first written, things have evolved. Is the above still a correct rephrasing of what's needed? |
Yes, that's correct. |
Opened a bunch of follow-up issues, so that we can track and prioritize future work on the ingress controller:
|
Also note #151 which tracks some additional issues relating to ingress rules vs. Istio's rules. |
As a proof of concept of the abstraction model we should implement standard Ingress support for Envoy. Should not need any additional configuration artifacts beyond what K8S supports today.
The text was updated successfully, but these errors were encountered: