You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you please put some guidance regarding how to connect to an existing tunnel, managed with Zero Trust Dashboard.
For the credentials.json I am using the output of cloudflared tunnel token , also I tried using the tunnel secret from that file to authorize with the tunnel. According to the cloudflare document its the only way to get authentication details for existing tunnel.
The text was updated successfully, but these errors were encountered:
Hey @drpdishant connecting to an existing tunnel is possible by setting either the CLOUDFLARE_TUNNEL_CREDENTIAL_FILE or CLOUDFLARE_TUNNEL_CREDENTIAL_SECRET in the secret referred by tunnel.spec.cloudflare.secret.
If using CLOUDFLARE_TUNNEL_CREDENTIAL_FILE, the whole file content (base64 encoded for k8s secret) should be used. If using CLOUDFLARE_TUNNEL_CREDENTIAL_SECRET, set it to the (base64 encoded) TunnelSecret field from the credential.json file.
If the above does not work for regular (non managed) tunnels, please attach a log from the controller-manager and I will try to reproduce the same.
But, tunnels managed by the Zero Trust Dashboard have not been tested, and might not work.
It is in the roadmap to support managed tunnels by making use of the Cloudflare APIs for configuration. See #47 (comment)
Can you please put some guidance regarding how to connect to an existing tunnel, managed with Zero Trust Dashboard.
For the credentials.json I am using the output of cloudflared tunnel token , also I tried using the tunnel secret from that file to authorize with the tunnel. According to the cloudflare document its the only way to get authentication details for existing tunnel.
The text was updated successfully, but these errors were encountered: