Live data from Hacker News

Exposing a web service with Cloudflare Tunnel

erisa.dev

1–10 of 186 posts

Re: Exposing a web service with Cloudflare Tunnel

#3
You can also put authentication in front of cloudflare argo tunnels, so you can securely expose internally hosted applications to the internet. A zero trust or BeyondCorp model is usally way easier than VPNs etc. It is a really nice alternative to hosting Buzzfeed SSO or Pomerium too.

Re: Exposing a web service with Cloudflare Tunnel

#7

I use this to expose services running in Kubernetes clusters and have Cloudflare tunnel pointing at my Kube gateways. It makes a ton of things like cluster failover much simpler than they otherwise would be.

Yup, and you can even have multiple tunnels that are load balanced, so that you don’t even have to fail over.

We have a single API service which is exposed to the internet, and put the CloudFlare tunnel as a sidecar inside the same pods. This way, it’s actually CloudFlare which handles the load balancing, which is surprisingly effective.

Re: Exposing a web service with Cloudflare Tunnel

#9

This looks pretty interesting to me. Self-hosting a webapp origin server on hardware in my house, fronted by CloudFlare... hmm. Food for thought.

As a matter of fact, I have a 4-node kubernetes cluster running at home which is exposed through a CloudFlare tunnel on the internet. Works like a charm, and you don’t have issues with firewalls, NAT, and/or dynamic IPs.

Re: Exposing a web service with Cloudflare Tunnel

#10

I use this to expose services running in Kubernetes clusters and have Cloudflare tunnel pointing at my Kube gateways. It makes a ton of things like cluster failover much simpler than they otherwise would be.

Could you elaborate on the setup a bit - for cluster fail over do you mean that since cloudflare is your frontend ingress you can easily point it to another cluster or is there more to it?
Post reply on HN