Cloudflare Ingress Controller Beta Feedback

@SamRhea wrote:

I apologize for how long it has taken for us to get you a clear answer. In the spirit of doing better I’ll start with the punchline: We plan to deprecate the Cloudflare Ingress Controller to focus on improvements to Argo Tunnel that make it easier to use with other, more capable, ingress controllers available.

We still think using Argo Tunnel and k8s together is an exceptionally good combination, but we have learned that running cloudflared as a sidecar is generally more reliable and faster than using our Ingress. Other Ingress controllers offer capabilities people want and need, and we don’t want to ask you to choose between them when adding Argo Tunnel. So, rather than continue to iterate on the controller that we built, we plan to invest more in Argo Tunnel itself.

Broadly, that means improvements to stability, monitoring, and management. We believe that work will be best for all Argo Tunnel users, including the k8s ones.

We have recently released documentation to help teams migrate to run the cloudflared daemon as a sidecar to any ingress controller or ELB. I know this is a small step, but we’re still committed to supporting k8s and Tunnel.

As a next step we will soon be releasing our own Docker image to implement the sidecar model and publishing it to container registries like DockerHub and GCR. You can expect that to be available before the end of the year.

Most importantly, we want to do a better job listening to users in forums like this. Please feel free to comment on this thread. We will be here to read it and respond.

Read full topic