-
-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to disable Cloudflare API integration #57
Comments
It makes more sense to disable DNS updates rather than complete API communication since tunnel lookups need the communication (at least right now, with the use case in #70), thus adding it to the TunnelBinding makes more sense to control it per binding, rather than per tunnel. |
It seems I still need to create a zone and define a domain in a |
With the introduction of proxied wildcard domains, the operator can be used in a mode where it does not talk to Cloudflare at all. Users can manually set a wildcard CNAME to whichever tunnel they create and let the operator handle the dynamic configuration of
cloudflared
.This can be a
Tunnel
/ClusterTunnel
CRD spec to disable DNS updates.The text was updated successfully, but these errors were encountered: