Add Kourier as an Ingress implementation option

[bbrowning]

In what area(s)?

/area networking
/area test-and-release

/kind proposal

Describe the feature

https://github.com/3scale/kourier is an Envoy-based Knative Ingress implementation. From their README:

Kourier is an Ingress for Knative. A deployment of Kourier consists of an Envoy proxy and a control plane for it. Kourier is meant to be a lightweight replacement for the Istio ingress. In the future, it will provide API management capabilities.

This project is under early development, but it already passes all the end-to-end tests of the Knative suite.

This proposal is to get Kourier added as an alternative Ingress option for Knative. Its primary goal is to be as small and lightweight of an Ingress implementation as possible specifically for Knative. It requires no extra CRDs and consists of two Deployments - one for the control plane pod and one for the data plane pods. It directly reconciles Knative Ingress objects into Envoy configuration.

The team behind Kourier would like to present their work at a future Networking WG meeting and I've already added it to the future topics section of that meeting doc. I've discussed this a bit in Slack with the networking team, but this issue is to track the feature request and facilitate discussion on GitHub with wider visibility.

[knative-prow-robot]

@bbrowning: The label(s) kind/proposal cannot be applied. These labels are supported: ``

In response to this:

In what area(s)?

/area networking
/area test-and-release

/kind proposal

Describe the feature

https://github.com/3scale/kourier is an Envoy-based Knative Ingress implementation. From their README:

Kourier is an Ingress for Knative. A deployment of Kourier consists of an Envoy proxy and a control plane for it. Kourier is meant to be a lightweight replacement for the Istio ingress. In the future, it will provide API management capabilities.

This project is under early development, but it already passes all the end-to-end tests of the Knative suite.

This proposal is to get Kourier added as an alternative Ingress option for Knative. Its primary goal is to be as small and lightweight of an Ingress implementation as possible specifically for Knative. It requires no extra CRDs and consists of two Deployments - one for the control plane pod and one for the data plane pods. It directly reconciles Knative Ingress objects into Envoy configuration.

The team behind Kourier would like to present their work at a future Networking WG meeting and I've already added it to the future topics section of that meeting doc. I've discussed this a bit in Slack with the networking team, but this issue is to track the feature request and facilitate discussion on GitHub with wider visibility.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.