apisix-ingress-controller

apisix-ingress-controller copied to clipboard

Knative is designed for serverless workloads on top of Kubernetes. Knative Serving runs scalable containers based on ingress gateway as its network layer. Currently, a few ingress gateway implementations such as Istio, Kong and Gloo are supported. APISIX ingress controller, however, is not among them.

This issue aims at exploring Knative ingress management mechanism and adding support for Knative. In other words, make APISIX ingress controller an alternative Knative network layer to manage ingress traffic.

Any suggestions or comments are welcome! And thanks @Yiyiyimu and @moonming for being mentors!

Interesting, welcome to submit proposals!

any news on the PRs?

Here is a PR I was working on to add support for Knative #606.

Thanks for your contribution, would you like to pick it up? @fhuzero

@tao12345666333 Thanks for the follow-up! So glad to see that the APISIX ingress controller project has grown a lot since when I created this issue.

My schedule is tight right now, but I'm willing to pick it up from where I left if I have time in the future. By the way, I'm curious about the development machine and environment for the project. Any recommendations for setting up the environment? I used to develop on an AWS EC2 instance but it cost a bit.

Typically, we use KIND to start a local cluster when developing locally, and deploy 1 replica of APISIX and etcd in it. That's enough.

In addition, if you don't want to develop locally, you can also choose a cloud environment like GitPod, which is also very convenient

Thank you for the info!