Considerations if not using cloudflare for dns or cloudflared #1017
onedr0p
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As it goes with Github, using cloudflare is also requirement for using this template. This is done to streamline the template without adding a ton of options to confuse people.
However with that said it is possible to use another DNS provider or not use Cloudflare Tunnels. Because there are so many options this isn't a guide on how to implement the DNS provider of your choosing but more of a rough overview of how it can be done.
All of this is assuming you have gone thru the steps in the README right up until running
task configure
Using Cloudflare DNS but removing Cloudflare Tunnels
This is the easiest method to do, it means your domain's DNS needs to be managed by Cloudflare. That can be done by updating the nameservers on your current DNS provider or transferring your domain to Cloudflare.
./bootstrap/tasks/validation/cloudflare.yaml
./bootstrap/tasks/validation/cli.yaml
./bootstrap/templates/kubernetes/apps/networking
./bootstrap/templates/kubernetes/apps/networking/kustomization.yaml.j2
and remove the line containingcloudflared
./bootstrap/templates/kubernetes/apps/networking/nginx/external/helmrelease.yaml.j2
--cloudflare-proxied
in./bootstrap/templates/kubernetes/apps/networking/external-dns/app/helmrelease.yaml.j2
./bootstrap/templates/kubernetes/apps/networking/nginx/external/dnsendpoint.yaml
./bootstrap/templates/kubernetes/apps/networking/nginx/external/kustomization.yaml
resources valuestask configure
and continue where that left off in the README.A
record in Cloudflare DNS pointing to your home IP address callingress
, make sure you have a way to update this record if you have a dynamic IP.Beta Was this translation helpful? Give feedback.
All reactions