From 73bed06eba0908c56ff1d9719baddcadd4c50b1e Mon Sep 17 00:00:00 2001 From: Devin Buhl Date: Wed, 5 Jul 2023 03:59:42 -0400 Subject: [PATCH] fix: use http2 for cloudflared --- .../apps/networking/cloudflared/app/configs/config.yaml | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/kubernetes/apps/networking/cloudflared/app/configs/config.yaml b/kubernetes/apps/networking/cloudflared/app/configs/config.yaml index c45f3a25..12b2778e 100644 --- a/kubernetes/apps/networking/cloudflared/app/configs/config.yaml +++ b/kubernetes/apps/networking/cloudflared/app/configs/config.yaml @@ -1,11 +1,8 @@ --- -# The `ingress` block tells cloudflared which local service to route incoming -# requests to. For more about ingress rules, see +originRequest: + http2Origin: true + # 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 `. -# 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