nydus
external-dns
nydus | external-dns | |
---|---|---|
3 | 79 | |
1,092 | 7,286 | |
2.0% | 1.1% | |
9.3 | 9.6 | |
14 days ago | 1 day ago | |
Rust | Go | |
Apache License 2.0 | 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.
nydus
-
Ask HN: Have You Left Kubernetes?
If you're pulling big images you could try kube-fledged (it's the simplest option, a CRD that works like a pre-puller for your images), or if you have a big cluster you can try a p2p distributor, like kraken or dragonfly2.
Also there's that project called Nydus that allows starting up big containers way faster. IIRC, starts the container before pulling the whole image, and begins to pull data as needed from the registry.
https://github.com/senthilrch/kube-fledged
https://github.com/dragonflyoss/Dragonfly2
https://github.com/uber/kraken
https://nydus.dev/
- Increase the speed of NPM install by more than 8 times
-
new "EROFS over Fscache" Linux container image architecture for CNCF Dragonfly Nydus
Nydus-fscache user guide: https://github.com/dragonflyoss/image-service/blob/master/docs/nydus-fscache.md
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?
plural - Deploy open source software on Kubernetes in record time. 🚀
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
docker-volume-hetzner - Docker Volume Plugin for accessing Hetzner Cloud Volumes
cloudflare-ingress-controller - A Kubernetes ingress controller for Cloudflare's Argo Tunnels
k8s-config-connector - GCP Config Connector, a Kubernetes add-on for managing GCP resources
ingress-nginx - Ingress-NGINX Controller for Kubernetes
swarmsible - Ansible based Tooling and production grade example Docker Stacks. Updated with new learnings from running Docker Swarm in production
crossplane - The Cloud Native Control Plane
Dragonfly2 - Dragonfly is an open source P2P-based file distribution and image acceleration system. It is hosted by the Cloud Native Computing Foundation (CNCF) as an Incubating Level Project.
PowerDNS - PowerDNS Authoritative, PowerDNS Recursor, dnsdist
terraform-cdk - Define infrastructure resources using programming constructs and provision them using HashiCorp Terraform
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖