feat!: add mandatory cloudflare tunnel support (#716)
Co-authored-by: Devin Buhl <onedr0p@users.noreply.github.com>
This commit is contained in:
1 parent
b917eccb76
commit
145f575fbb
34 files changed
+525
-568
No files matched your search
@@ -0,0 +1,18 @@
|
||||
---
|
||||
# The `ingress` block tells cloudflared which local service to route incoming
|
||||
# requests to. For more about ingress rules, see
|
||||
# https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/configuration/ingress
|
||||
#
|
||||
# Remember, these rules route traffic from cloudflared to a local service. To route traffic
|
||||
# from the internet to cloudflared, run `cloudflared tunnel route dns <tunnel> <hostname>`.
|
||||
# E.g. `cloudflared tunnel route dns example-tunnel tunnel.example.com`.
|
||||
ingress:
|
||||
- hostname: "${SECRET_DOMAIN}"
|
||||
service: https://ingress-nginx-controller.networking.svc.cluster.local:443
|
||||
originRequest:
|
||||
originServerName: "ipv4.${SECRET_DOMAIN}"
|
||||
- hostname: "*.${SECRET_DOMAIN}"
|
||||
service: https://ingress-nginx-controller.networking.svc.cluster.local:443
|
||||
originRequest:
|
||||
originServerName: "ipv4.${SECRET_DOMAIN}"
|
||||
- service: http_status:404
|
||||
Reference in new issue
Block a user