external-dns
awesome-home-kubernetes
Our great sponsors
external-dns | awesome-home-kubernetes | |
---|---|---|
79 | 16 | |
7,242 | 1,205 | |
1.7% | - | |
9.6 | 7.7 | |
about 24 hours ago | over 1 year ago | |
Go | Python | |
Apache License 2.0 | The Unlicense |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
external-dns
-
Upgrading Hundreds of Kubernetes Clusters
The second one is a combination of tools: External DNS, cert-manager, and NGINX ingress. Using these as a stack, you can quickly deploy an application, making it available through a DNS with a TLS without much effort via simple annotations. When I first discovered External DNS, I was amazed at its quality.
-
Kubernetes External DNS provider for Hetzner
One of the reasons why I chose Hetzner was that it WAS supported by the ExternalDNS project. I didn't quite understand why the Hetzner provider was pulled, but I saw that an attempt of re-adding it was refused, on the ground that the upcoming webhook architecture would have allowed to better maintain providers.
-
Istio Multi-Cluster Setup
Write a custom controller for the external DNS controller, or setup some form of ArgoCD app / appset templating.
-
Looking for ExternalDns alternative for non k8s environment
so I am looking at having an automated way for new routers registered in Traefik to also have the corresponding DNS entry added to my Pihole instance similar to external-dns but obviously, this is exclusive to ingress on k8s environments. my current setup is traefik in a container on unraid.
-
Is a Load Balancer necessary for a HA Cluster?
You technically don’t need to run a load balancer or have a virtual IP for your control plane. If you control your dns, you can add an A record pointing to all IPs for your control plane nodes. It won’t load balance your traffic, but combined with something like External DNS it gives you HA for the control plane.
-
How can I assign an EIP to a Kubernetes deployment?
I normally deploy external-dns, which automatically updates DNS with the ingress controller's external IP address.
-
Registering DNS with Windows Domain DNS
Background: Having a look I can see this https://github.com/kubernetes-sigs/external-dns
-
Cluster nodes on different networks
3) Use the Kubernetes External-DNS. I've never used this, but this is assuming it can update DNS for each pods/app to point to the correct Node (it'd need to update my Homelab DNS running on Windows Server)
-
I am stuck on learning how to provision K8s in AWS. Security groups? ALB? ACM? R53?
So here’s the solution I have taken for our current stack. EKS and its dependencies are created through terraform using the eks module as well as provision a route53 subdomain and a wildcard cert. Once we have that created, I have installed this deployment into the cluster via the helm module: https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/. This allows me to use kuberentes resources (load balancers or ingress objects) and it will handle all the provisioning of load balancers and security groups for me, based on my application yaml and annotations. We also use https://github.com/kubernetes-sigs/external-dns to manage all of our specific host names for the applications through annotations. So to generally put, terraform manages out Kubernetes clusters, and Kubernetes manages the deployment of anything needed for the application including volumes, load balancers, hostnames though Kubernetes system deployments
-
How to expose services/apps to my home network with custom DNS names
Metallb for your load balancer (layer2 mode will do) NginX-ingress, will be spot on for internal home apps External-dns to publish your dns record to your Dns server at home, https://github.com/kubernetes-sigs/external-dns
awesome-home-kubernetes
-
A 4+1 node storage cluster intended for AI ingest datasets. What platform should we use? (ceph, btrfs, OpenZFS, TruNas Scale?
Also check out the awesome kubernetes@home repo where many homelabbers share their configs.
-
Running Kubernetes cluster locally to self host a bunch of applications along with a DNS server
Sorry I'm not familiar with this. Are you referring to this?
-
to kube or not to kube?
https://github.com/k8s-at-home/awesome-home-kubernetes https://github.com/k8s-at-home/template-cluster-k3s
- I must announce the immediate end of service of SSLPing
-
Deploy a Kubernetes cluster and have it automated from a Git repository!
To see it in action be sure to check out my repository or the many others here.
-
[github] k3s-io/k3s: Production ready, easy to install, half the memory, all in a binary less than 100 MB
Make it usable and link to the best place with k3s in action: https://github.com/k8s-at-home/awesome-home-kubernetes
- k8s-at-home/awesome-home-kubernetes: Awesome projects involving running Kubernetes at home
-
Kubernetes at Home With K3s
Nice but I suggest going to https://github.com/k8s-at-home/awesome-home-kubernetes and learn from the best at this topic ;)
-
Kubernetes best practices generally and for organizing my stuff
Check out Flux V2. It syncs a git repo with your cluster, allowing you to define your infrastructure as code. It will keep your cluster synced with your repo and detect changes. A number of example repos are Here and onedr0p did a example repo here There's many options for structuring folder, I'd recommend you have a look at a few repos and pick one you like. The linked template is a good start, as it helps avoid dependency hell with a crd folder that starts before the YAML that needs the crd defined. Many people on the awesome list also run ansible for full infrastructure as code. I spent a lot of time perfecting my setup to go from blank Ubuntu VM to my cluster with a few keystrokes. Running it in git also helps you be able to use things like renovate bot to keep versions up to date. As for namespaces, everyone had their own method, but about using kube-system. Also, keep a eye out for services that refuse to have their name space changed.
What are some alternatives?
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
watchtower - A process for automating Docker container base image updates.
cloudflare-ingress-controller - A Kubernetes ingress controller for Cloudflare's Argo Tunnels
cluster-template - A template for deploying a Kubernetes cluster with k3s or Talos
ingress-nginx - Ingress-NGINX Controller for Kubernetes
longhorn - Cloud-Native distributed storage built on and for Kubernetes
crossplane - The Cloud Native Control Plane
awesome-gitops - A curated list for awesome GitOps resources
PowerDNS - PowerDNS Authoritative, PowerDNS Recursor, dnsdist
piku - The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
rook - Storage Orchestration for Kubernetes