Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
external-dns
Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
kube-vip - When using a cluster with a highly available control plane you need to have a load balancer. You have many options for this, you can use an external load balancer like HAProxy or Nginx or even keepalived. Using any of those options means you have to set up configuration outside the cluster, with kube-vip this is handled in the cluster. kube-vip can also me a replacement for metallb or klipper (servicelb) but there are drawbacks to using this for k8s services.
klipper (servicelb) is a very basic implementation of a load balancer, reading thru the issues you'll soon discover there's many reasons why metallb is preferred. For example klipper only supports externalTrafficPolicy: Cluster which means the real source IP of the request is not passed thru to the pod. The pod only gets the LB IP.
https://github.com/kubernetes-sigs/external-dns is another way to expose ingress and load balancer IPs to an external (from the cluster) dns server.