From c02b825e7db91e793bd28b89519780a350a19cd9 Mon Sep 17 00:00:00 2001 From: Ryan Dellolio Date: Tue, 14 Feb 2023 23:09:39 -0500 Subject: [PATCH] Provide direct link to docs and httpHostHeader example --- named-tunnel-k8s/cloudflared.yaml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/named-tunnel-k8s/cloudflared.yaml b/named-tunnel-k8s/cloudflared.yaml index 31af0b5..7b70911 100644 --- a/named-tunnel-k8s/cloudflared.yaml +++ b/named-tunnel-k8s/cloudflared.yaml @@ -65,6 +65,8 @@ spec: # It's useful to define it in k8s, rather than as a stand-alone .yaml file, because # this lets you use various k8s templating solutions (e.g. Helm charts) to # parameterize your config, instead of just using string literals. +# For more about configuration parameters and their default settings, see +# https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/tunnel-guide/local/local-management/ingress/#origin-configuration apiVersion: v1 kind: ConfigMap metadata: @@ -91,6 +93,7 @@ data: # The first rule proxies traffic to the httpbin sample Service defined in app.yaml - hostname: tunnel.example.com service: http://web-service:80 + httpHostHeader: tunnel.example.com # This rule sends traffic to the built-in hello-world HTTP server. This can help debug connectivity # issues. If hello.example.com resolves and tunnel.example.com does not, then the problem is # in the connection from cloudflared to your local service, not from the internet to cloudflared.