aws-load-balancer-controller VS aws-alb-ingress-controller

I thought at the beginning that such certificate would then expire, but I have seen cert-manager is within ALB code https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/config/certmanager/certificate.yaml so that makes me hesitate about it.

Detailed behavior changes can be found in the release notes for version 2.6.0 of the AWS Load Balancer Controller. https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases The key points include:

If you are using Kubernetes, you can enable security groups on your NLB by using AWS Load Balancer controller version 2.6.0 or later. Enabling NLB security groups using the controller enhances the nodes' security, as inbound rules can be simplified by referencing the NLB security groups. It also provides scaling improvements, as the controller keeps a constant number of security group rules per cluster.

I use the AWS Load Balancer Controller: https://github.com/kubernetes-sigs/aws-load-balancer-controller.

You can install the AWS Load Balancer Controller, and then create an "Ingress" when you install your Nginx Ingress controller, possible with some necessary annotations.

aws-load-balancer-controller

Yes. Google's ingress controller talks to the GCP API and spins up an HTTP LB for you. The AWS LB Controller handles provisioning ALB's for you. And ... I guess other clouds exist too but these are the ones I am familiar with.

NLB don't support weighted target groups and for some reason are extremely slow when adding instances o removing them from target groups, which makes deployments a bit meh (old instances and new instances can be receiving traffic at the same time for up to 2 mins)

I've installed and configured AWS ALB Ingress Controller(https://github.com/kubernetes-sigs/aws-alb-ingress-controller) and it's working properly over HTTP. However, it doesn't resolve over HTTPS.

------------------------------------------------------------------------------- AWS ALB Ingress controller Release: v1.1.4 Build: git-0db46039 Repository: https://github.com/kubernetes-sigs/aws-alb-ingress-controller.git------------------------------------------------------------------------------- W0611 19:58:20.627965 1 config.go:46] Environment variable configuration is deprecated, switch to the --aws-region flag. W0611 19:58:20.628326 1 client_config.go:549] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. F0611 19:58:20.761520 1 main.go:97] no matches for kind "Ingress" in version "extensions/v1beta1"