plural
external-dns
Our great sponsors
plural | external-dns | |
---|---|---|
21 | 79 | |
1,304 | 7,242 | |
2.1% | 1.7% | |
9.1 | 9.6 | |
9 days ago | 7 days ago | |
TypeScript | Go | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
plural
-
Curious if anyone has adopted a stack to do raw data ingestion in Databricks?
I’ve just recently found out about plural. Perhaps give them a try? I think they have a cool idea for quickly deploying an ELT infrastructure. Perhaps check them out?
- Self-Hosted Open-Source Alternative to a Managed Service
- Plural - An open-source alternative to managed services
- An open-source alternative to managed services
- GitHub - pluralsh/plural: Deploy open source software on Kubernetes in minutes
- Deploy open-source software on Kubernetes in record time.
- OSS Kubernetes App deployment platform
- Show HN: Plural.sh-Deploy, secure and scale open-source apps on your cloud
- OSS Kubernetes App Deployment platform built on Elixir
- Deploy open-source software in your own Kubernetes cluster within minutes.
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
What are some alternatives?
werf - A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
kube-fledged - A kubernetes operator for creating and managing a cache of container images directly on the cluster worker nodes, so application pods start almost instantly
cloudflare-ingress-controller - A Kubernetes ingress controller for Cloudflare's Argo Tunnels
nixery - Container registry which transparently builds images using the Nix package manager. Canonical repository is https://cs.tvl.fyi/depot/-/tree/tools/nixery
ingress-nginx - Ingress-NGINX Controller for Kubernetes
kraken - P2P Docker registry capable of distributing TBs of data in seconds
crossplane - The Cloud Native Control Plane
docker-volume-hetzner - Docker Volume Plugin for accessing Hetzner Cloud Volumes
PowerDNS - PowerDNS Authoritative, PowerDNS Recursor, dnsdist
k8s-config-connector - GCP Config Connector, a Kubernetes add-on for managing GCP resources
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖