inlets
external-dns
inlets | external-dns | |
---|---|---|
10 | 79 | |
1,315 | 7,286 | |
0.7% | 1.1% | |
7.1 | 9.6 | |
4 months ago | about 19 hours ago | |
Go | Go | |
MIT License | 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.
inlets
-
How to bypass CGNAT and expose your server to the internet using ZeroTier, a VPS and NGINX
Thanks for the guide. Just to mention another option is https://github.com/inlets/inlets-operator
-
How to deploy my first Docker (Compose) application to the cloud?
adding on to this, if OP goes down the local k8s cluster route for learning purposes, they can then hook it up to a public load balancer with this TCP tunnel thingy called inlets for a few bucks a month https://github.com/inlets/inlets-operator
- Ask HN: Those making $500/month on side projects in 2021 – Show and tell
- Using external-dns on-prem (ideas welcome)
- Show HN: Inlets-Operator (0.12.1) adds support for Hetzner LoadBalancers
- Show HN: Inlets-operator (0.12.1) adds support for Hetzner
- Remote Access Poll (redo)
- Can Anyone Recommend A Free Opensource
-
Exploring Kubernetes Operator Pattern
Thanks! To be honest, I was thinking of a tutorial too. But then I stumbled upon the inlets-operator (the one from the visualization in the article) and its code actually looks very good in my opinion. It's concise, straightforward, and seems to be idiomatic. I do recommend taking a look at it.
- Add public LoadBalancers to your local Kubernetes clusters
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?
sish - HTTP(S)/WS(S)/TCP Tunnels to localhost using only SSH.
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
traefik - The Cloud Native Application Proxy
cloudflare-ingress-controller - A Kubernetes ingress controller for Cloudflare's Argo Tunnels
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
ingress-nginx - Ingress-NGINX Controller for Kubernetes
iodine - Official git repo for iodine dns tunnel
crossplane - The Cloud Native Control Plane
socks5-proxy-server - SOCKS5 proxy server
PowerDNS - PowerDNS Authoritative, PowerDNS Recursor, dnsdist
Squid - Squid Web Proxy Cache
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖