metallb VS ingress-nginx

Not to take anything away from OP but MetalLB also provides local load balancing.

Quoting from their docs:

metalLB to manage bare-metal LoadBalancer services - WIP - Only L2 configuration can be set-up via playbook.

MetalLB

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/

metalLB to manage bare-metal LoadBalancer services - WIP - Only L2 configuration can be set-up via playbook.

-- MetalLB

Shameless Plug: Here's one of my dashboards I made for Ingress-Nginx, which is my recommended border router/gateway into all the services. It adds deep robust metrics and configurability, and if you've got years of experience with Nginx also, it allows you rich complex customization via nginx's configuration structure via kubernetes annotations. Besides that I have open-source helm charts which are easy to use, boilerplates showing how to use them, a volume autoscaler to automatically resize your disks as they get full, and a blog where I share various of my experience which is a companion blog to my upcoming book of the same name. Hope this helps! Feel free to ask if you have any further questions.

nginx-ingress-controller, haproxy-ingress-controller or contour-ingress-controller for ingress management.

Snippets are however unsafe and need to be disabled if there is more than 1 team with permissions on the cluster: https://github.com/kubernetes/ingress-nginx/issues/7837

Yeah, the documentation is a bit lackluster. This could be the fix, but the PR documentation is vague and I will not analyze the changes made, but could be: https://github.com/kubernetes/ingress-nginx/pull/8456

For example, ubuntu.com (which I work on during my day job) still doesn't support HTTP/3. This is because getting it into Kubernetes seems to be taking a while. It sounds like it won't land until NGINX merge it into their stable release.

You might want to have a look at the long-standing bug from 2021. If that is possible in the meantime please correct me and show me an example ;)

Also, of personal note, I highly recommend you use the "ingress-nginx" controller which has a huge community and is of much higher quality and flexibility than the "nginx-ingress controller by nginx inc". I've had a lot of success with dozens of clients with this controller. It rocks!

[email protected]:~$ [email protected]:~$ curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash 100 11345 100 11345 0 0 45436 0 --:--:-- --:--:-- --:--:-- 45562 Downloading https://get.helm.sh/helm-v3.10.3-linux-amd64.tar.gz Verifying checksum... Done. Preparing to install helm into /usr/local/bin helm installed into /usr/local/bin/helm [email protected]:~$ helm ls NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION [email protected]:~$ helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx "ingress-nginx" has been added to your repositories [email protected]:~$ helm repo update Hang tight while we grab the latest from your chart repositories... ...Successfully got an update from the "ingress-nginx" chart repository Update Complete. ⎈Happy Helming!⎈ [email protected]:~$ helm install ingress-nginx ingress-nginx/ingress-nginx \ --create-namespace \ --namespace ingress-nginx NAME: ingress-nginx LAST DEPLOYED: Wed Dec 21 21:39:08 2022 NAMESPACE: ingress-nginx STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: The ingress-nginx controller has been installed. It may take a few minutes for the LoadBalancer IP to be available. You can watch the status by running 'kubectl --namespace ingress-nginx get services -o wide -w ingress-nginx-controller' [email protected]:~$ kubectl get po,svc -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system pod/local-path-provisioner-79f67d76f8-5rxs8 1/1 Running 0 17m kube-system pod/coredns-597584b69b-g2rbs 1/1 Running 0 17m kube-system pod/metrics-server-5c8978b444-hp822 1/1 Running 0 17m metallb-system pod/controller-84d6d4db45-j49mj 1/1 Running 0 10m metallb-system pod/speaker-pnzxw 1/1 Running 0 10m metallb-system pod/speaker-rs7ds 1/1 Running 0 10m metallb-system pod/speaker-pr4rq 1/1 Running 0 10m ingress-nginx pod/ingress-nginx-controller-8574b6d7c9-frtw7 1/1 Running 0 2m47s NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE default service/kubernetes ClusterIP 10.43.0.1 443/TCP 18m kube-system service/kube-dns ClusterIP 10.43.0.10 53/UDP,53/TCP,9153/TCP 18m kube-system service/metrics-server ClusterIP 10.43.249.247 443/TCP 18m metallb-system service/webhook-service ClusterIP 10.43.4.24 443/TCP 10m ingress-nginx service/ingress-nginx-controller-admission ClusterIP 10.43.125.197 443/TCP 2m47s ingress-nginx service/ingress-nginx-controller LoadBalancer 10.43.110.31 10.124.110.210 80:32381/TCP,443:30453/TCP 2m47s

Verify that the values in your values.yaml file match the values in the example file from the nginx ingress controller's Helm chart (https://github.com/kubernetes/ingress-nginx/blob/main/charts/ingress-nginx/values.yaml). In particular, check that all required values are present and that they are in the correct format.