Updated cloudflared

[acrogenesis]

Cloudflared version for this project is 8 versions behind, there's been lot's of new features and bug fixes https://github.com/cloudflare/cloudflared/releases

[chris-erickson]

@mattalberts what's up here? We're wanting to build critical tools on this but it's a ghost town everywhere. Some sort of roadmap would be appreciated.

[acrogenesis]

@a-robinson
@aaranmcguire
@acmacalister
@adamschwartz
@ahrex
@ashleygwilliams
@Bren2010
@BURO9
@cbroglie
@dknecht
@dotjs
@dqminh
@eaufavor
@echtish
@eiginn
@ejcx
@ghedo
@grittygrease
@harrishancock
@hturan
@IcyApril
@ignatk
@inikulin
@jamesog
@jayapriya90
@jejenone
@jensechu
@jimenezrick
@jrf0110
@jroyal
@junho Choi
@junhochoi
@kentonv
@lgarofalo
@Margatroid
@markpash
@mattalberts
@mihirjham
@mstremante
@nickbalestra
@patryk
@prestonp
@punkeel
@renandincer
@rita3ko
@scotchmist
@signalnerve
@skepticfx
@terinjokes
@tlianza
@toekneestuck
@vasturiano
@xtuc

Somebody knows if Cloudflare is planning on keeping support for this ingress controller?

[zackbloom]

Sorry for the delay and the lack of communication. We want to invest more in Kubernetes but have been very focused on improvements to Argo Tunnel itself. I'm sorry we haven't communicated better, we will have a more detailed update in the next few days.

[acrogenesis]

Thanks @zackbloom for the reassurance. Sorry for the carpet bomb but we and I assume many others are heavily invested in Cloudflare and Kubernetes 👍

[TownLake]

As @zackbloom said, thank you for being patient, and 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.

[davidkarlsen]

Any update on providing a ready-baked image?

[TownLake]

Releasing the image is still on our list, but not just ready yet. We're planning to have that available in the next couple months.

Thanks for your patience, we know this will help improve the ergonomics for this use case. Right now we're heads down on improving Tunnel stability overall, which has improved since the last response here, but we aren't done just yet. Once there, we're going to keep making usability better with things like releasing the image.

[davidkarlsen]

Also cloudflare/cloudflared#110 is ripe. After all cloudflared is used to get your apps online from lockdown envs - using standard ports and infra is part of that deal.