feat: Support remotely-managed cloudflare tunnels

[jfroy]

No description provided.

[onedr0p]

I wonder if there's a better way to name locally vs remotely managed tunnels? It might be because it's early but this confused me a bit at first 😅

Maybe cli-created vs web-created?

[jfroy]

I wonder if there's a better way to name locally vs remotely managed tunnels? It might be because it's early but this confused me a bit at first 😅

Maybe cli-created vs web-created?

I borrowed those terms straight from cloudflare for consistency. https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/get-started/. But based on that document as well, could use "CLI" vs "dashboard".

[mrueg]

Alternatively, we could use https://github.com/adyanth/cloudflare-operator which would allow changes after the cluster has been bootstrapped.

[jfroy]

Alternatively, we could use https://github.com/adyanth/cloudflare-operator which would allow changes after the cluster has been bootstrapped.

Technically the only thing that's required to use a remotely-managed tunnel is to set the TUNNEL_TOKEN env var. If it is set to a non-empty value, cloudflared will use it, otherwise it will continue and use the credentials file. So all someone would need to do is edit the secret. We would need to edit the PR to not have the template conditionals in the secret definition and in the helm release.

https://github.com/cloudflare/cloudflared/blob/master/cmd/cloudflared/tunnel/subcommands.go#L656

[onedr0p]

Alternatively, we could use https://github.com/adyanth/cloudflare-operator which would allow changes after the cluster has been bootstrapped.

That would be nice but the release and commit history on it doesn't give me confidence that it's well supported.

[onedr0p]

@jfroy I am getting some support requests that make this a bit confusing to people. I may just go back to CLI-only created and managed tunnels.

[jfroy]

@jfroy I am getting some support requests that make this a bit confusing to people. I may just go back to CLI-only created and managed tunnels.

Totally fair. I wasn't comfortable with yet more secrets in plaintext under my home directory, so I went with a dashboard tunnel.