External-dns Alternatives
Similar projects and alternatives to external-dns
-
metallb
A network load-balancer implementation for Kubernetes using standard routing protocols
-
cert-manager
Automatically provision and manage TLS certificates in Kubernetes
-
-
-
-
-
-
-
Scout APM
Scout APM: A developer's best friend. Try free for 14-days. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
-
-
-
-
-
speedtest
Self-hosted Speedtest for HTML5 and more. Easy setup, examples, configurable, mobile friendly. Supports PHP, Node, Multiple servers, and more
-
-
kube-karp
☸ Add a floating virtual IP to Kubernetes cluster nodes for load balancing easily.
-
template-cluster-k3s
Highly opinionated template for deploying a single k3s cluster with Ansible and Terraform backed by Flux and SOPS.
-
Home Assistant
:house_with_garden: Open source home automation that puts local control and privacy first.
-
Grafana
The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
-
Vault
A tool for secrets management, encryption as a service, and privileged access management
-
Dokku
A docker-powered PaaS that helps you build and manage the lifecycle of applications
-
Reviews and mentions
-
Choosing a Combo DNS Registrar & Email Provider w/ K8s Ext-DNS support
Hi everyone! I'm looking for some input on selecting a service provider who offers both DNS Registration services and Email hosting. In addition, the service provider must be supported by the Kubernetes External DNS project.
-
A webhook for injecting caddy sidecars into Kubernetes Pods
I was using pihole local DNS to maintain some short records for myself. I eventually wanted to automate that process with external dns which led to this PR ( go throw it some love if you want to see Pi-Hole support in ExternalDNS :D ). Anyway, with that running locally in my cluster I realized I no longer had need for Ingress. My fork creates the records for services automatically in Pi-Hole, and calico makes the IP addresses routable across the house :D :D. Last but not least, I lost automatic TLS by taking Ingress out of the equation (I like the lock in my browser, even internally).
-
Ask HN: Solo-preneurs, how do you DevOps to save time?
Via annotations on my ingresses, and of course with this : https://github.com/kubernetes-sigs/external-dns
-
Ask HN: Does anyone use a fully Kubernetes-native stack at home/work?
I guess that would really depend on your setup. It would differ significantly if you’re doing virtualised nodes ontop of vmware/proxmox/qemi/etc, if you’re doing single node with storage, or if you’re doing something more exotic like raspberry pis with either one node with storage or external nas.
I have a couple of different setups (mostly for fun), which are pretty simple. Main things I use are a csi driver to allow me to use my trunas scale as storage (https://github.com/democratic-csi/democratic-csi), cloudflare’s argo tunnel to expose my clusters to the outside world (https://github.com/cloudflare/cloudflare-ingress-controller), an operator for managing external dns with cloudflare (https://github.com/kubernetes-sigs/external-dns/blob/master/...). Everything else is pretty much they way any other cluster would look.
- Should custom controllers manage external resources?
-
Can I rely on the NLB hostname having the resource name in it?
Last, you can use use the external-dns service to auto-update your record to a friendly alias, in R53: https://github.com/kubernetes-sigs/external-dns
- How are you doing DNS?
-
Suggestions for load balancer setup
You might want to look at the external DNS service https://github.com/kubernetes-sigs/external-dns to create fqdns directly to your nginx ingress services.
-
It took almost a full day, but I finally got a decent homelab diagram :D Feedback is most welcome!
Yeah, I’ve been trying to solve this myself but haven’t found a good way. I was hoping to use external-dns but that unfortunately seemed like a dead end. But I guess it could update coreDNS if it was running on OPNsense though. Would that be comparable to the setup you’ve got?
- ECS migrate to EKS part 3
-
How do you manage external-dns on EKS with route53 when you have multiple services / domain names and are using Helm to spawn each service into a different environment (prod, staging, etc.)?
Hmm, but if you check out the tutorial for working with Route 53 at https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md it mentions that the txt-owner-id is the Zone ID from Route 53.
I wrote a detailed question about this here: https://github.com/kubernetes-sigs/external-dns/discussions/2155
-
Using external-dns on-prem (ideas welcome)
I opened this GH issue over a year ago but there's no movement on it, however there are some workarounds posted in the replies.
-
Need a CNAME and TXT record with the same name
According to this link there is a way around it using --txt-prefix but I have no idea how to implement this. I've searched Google for --txt-prefix and I come across many posts saying it's the solution and that said flag exists but none that say how to apply said flag. I'm hoping someone can help me figure out how to make my needed TXT and CNAME live together in harmony...or at least look like they do when a DNS request is made.
-
Kubernetes, external-dns, Pi-hole and a custom domain
external-dns is my tool of choice to handle the synchronization between my Ingresses and the DNS provider; on my local network, I use Pi-hole to filter all my DNS request and to block some of them.
Stats
kubernetes-sigs/external-dns is an open source project licensed under Apache License 2.0 which is an OSI approved license.
Popular Comparisons
Are you hiring? Post a new remote job listing for free.