Skip to content
This repository has been archived by the owner on Jun 14, 2018. It is now read-only.

Implement Ingress Controller for Envoy #6

Closed
louiscryan opened this issue Dec 12, 2016 · 6 comments
Closed

Implement Ingress Controller for Envoy #6

louiscryan opened this issue Dec 12, 2016 · 6 comments
Assignees

Comments

@louiscryan
Copy link

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.

@kyessenov
Copy link
Contributor

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.

@elevran elevran self-assigned this Jan 23, 2017
@elevran
Copy link

elevran commented Jan 23, 2017

@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:
Run the manager as an ingress controller to setup Envoy as a standard Ingress controller, only basic k8s Ingress functionality. Later extend to support full Istio functionality.

Since this issue was first written, things have evolved. Is the above still a correct rephrasing of what's needed?

@louiscryan
Copy link
Author

Yes, that's correct.

@elevran
Copy link

elevran commented Feb 23, 2017

Merged in #71 #177

@elevran elevran closed this as completed Feb 23, 2017
@zcahana
Copy link
Member

zcahana commented Feb 27, 2017

Opened a bunch of follow-up issues, so that we can track and prioritize future work on the ingress controller:

@zcahana
Copy link
Member

zcahana commented Feb 27, 2017

Also note #151 which tracks some additional issues relating to ingress rules vs. Istio's rules.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants