aws-load-balancer-controller VS kompose

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)

Install Kompose - a conversion tool that allows you to convert your Docker Compose code to Kubernetes configuration files Run kompose convert in the same directory as your docker-compose.yml to generate the config files for your Kubernetes cluster

Kubernetes (via kompose)

As stated on their homepage, with Kompose, you can now push the same file to a production container orchestrator!. The tool definitely covers a wide range of Kubernetes features, among which these are meaningless locally but crucial for kubernetes :

K3s is a small, open source, no nonsense, distribution of Kubernetes. I think you'll find it just as easy to setup as Swarm. The challenge will be that Kubernetes has an entirely different API compared to Docker/Docker Compose. This can be mitigated by a tool called kompose, but using this will limit what you can do on Kubernetes.

Although I recently moved my own services from docker compose to kubernetes using https://kompose.io/ and now the only thing I run with docker compose, currently, is my private docker registry but everything including in kube, are always in their own folders.

I haven't run into the need to do that, but there is the Kompose project that exists to help with the conversion (https://kompose.io/)!

Compose claims to do that. https://kompose.io and https://kubernetes.io/docs/tasks/configure-pod-container/translate-compose-kubernetes/