metallb
external-dns
Our great sponsors
metallb | external-dns | |
---|---|---|
78 | 78 | |
6,554 | 7,188 | |
2.0% | 2.7% | |
9.4 | 9.6 | |
6 days ago | 6 days ago | |
Go | 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.
metallb
-
Trouble with RKE2 HA Setup: Part 2
To avoid that, you can use a combination of haproxy and keepalived, an enterprise grade load balancer like the one from F5 or Citrix. Besides that you can also work with https://kube-vip.io or https://metallb.universe.tf.
-
Kubernetes and feeling defeated
Not sure if klipper is usable in a cluster with multiple nodes, as it binds to one port only. You may want to use MetalLB instead: https://metallb.universe.tf/
-
Cool stuff to deploy for a project ideas
Then deploy MetalLB https://metallb.universe.tf/
-
PaperLB: A Kubernetes Network Load Balancer Implementation
Not to take anything away from OP but MetalLB also provides local load balancing.
Quoting from their docs:
-
libvirt-k8s-provisioner - Ansible and terraform to build a cluster from scratch in less than 10 minutes ok KVM - Updated for 1.26
metalLB to manage bare-metal LoadBalancer services - WIP - Only L2 configuration can be set-up via playbook.
-
Créer des applications directement dans Kubernetes avec Acorn …
MetalLB
- Loadbalancer is always pending
-
How hard is it to deploy kubernetes on bare metal in 2022 ?
Set up MetalLB https://metallb.universe.tf/ either via helm or simple manifest. Pick a range of ips to allocate, and assign via manifest https://metallb.universe.tf/configuration/
- Kubernetes e netstat
external-dns
-
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.
-
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
-
Kubernetes as a Platform vs. Kubernetes as an API
Disclaimer: I work for AWS but had nothing to do with this blog post (I'm seeing it for the first time with everyone else here).
I think this is an unfair summary of the post. Of course, using Kubernetes to orchestrate other AWS services is going to be a go-to example on the _AWS_ blog, but there is plenty of vendor-agnostic software doing similar things: DNS Records[1], Databases[2], even using Kubernetes CRDs to deploy Kubernetes[3].
The idea of using Kubernetes as an API to orchestrate external resources doesn't inherently lock you into any single vendor.
-
Does it make sense to use nginx on top of the ingress-nginx
For the average developer an Ingress is substantially simpler to understand. For an expert such as yourself there are additional annotations which may be added, to use nginx specfic features. However the big win using the nginx ingress controller is integration with other Kubernetes features like cert manager and External DNS
-
Kubernetes external-dns add support for pi-hole in the latest release
In the latest version v0.13.2 add support for pi-hole as a dns provider:
-
Help me understand real use cases of k8s, I can’t wrap my head around it
external-dns
- Dont understand how I can watch external resources modification/deletion with my custom operator
-
cloudflare and ingress-nginx
I can then set annotations on the Ingress resource to tell external-dns to flip the proxy switch on the DNS record in Cloudflare:
-
Istio woes on eks 1.22 - external-dns version stuck to v0.7.2
according to users in this issue they claim the external-dns image being a cause of their dns failing on kubernetes 1.22. https://github.com/kubernetes-sigs/external-dns/issues/961
What are some alternatives?
kube-vip - Kubernetes Control Plane Virtual IP and Load-Balancer
calico - Cloud native networking and network security
ingress-nginx - Ingress-NGINX Controller for Kubernetes
cloudflare-ingress-controller - A Kubernetes ingress controller for Cloudflare's Argo Tunnels
crossplane - The Cloud Native Control Plane
PowerDNS - PowerDNS Authoritative, PowerDNS Recursor, dnsdist
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
cert-manager - Automatically provision and manage TLS certificates in Kubernetes
rancher - Complete container management platform
kube-plex - Scalable Plex Media Server on Kubernetes -- dispatch transcode jobs as pods on your cluster!
k3s - Lightweight Kubernetes