Argo Tunnel Ingress Controller provides Kubernetes Ingress via Argo Tunnels. The controller establishes or destroys tunnels by monitoring changes to resources.
Argo Tunnel offers an easy way to expose web servers securely to the internet, without opening up firewall ports and configuring ACLs. Argo Tunnel also ensures requests route through Cloudflare before reaching the web server so you can be sure attack traffic is stopped with Cloudflare’s WAF and Unmetered DDoS mitigation and authenticated with Access if you’ve enabled those features for your account.
kubectl apply -f deploy/argo-tunnel.yamlUpdate the
ServiceAccountnamespace and bindings to deploy in an alternate namespace.
Without role based access control (RBAC).
kubectl apply -f deploy/argo-tunnel-no-rbac.yamlWith Helm.
helm install --name anydomain cloudflare/argo-tunnelNote: replicas >1 requires load-balancers
- Argo Tunnel: Reference
- Argo Tunnel: Quick Start
- Deploying with Helm
- Setup Your First Tunnel
- Setup Tunnels to Subdomains
- Setup High Availability with Load Balancers
- Supported Command-Line Options, Annotations & Labels
- Monitoring & Analytics
Thanks in advance for any and all contributions!
- Before contributing, please familiarize yourself with the Code of Conduct
- See contributing to setup your environment.
- Checkout the issues and roadmap.
The Cloudflare community forum is a place to discuss Argo, Argo Tunnel, or any Cloudflare product.