awx-operator VS aws-load-balancer-controller

We're happy to announce that AWX Version 23.0.0 is now available! We're happy to announce that AWX Operator version 2.5.2 is now available!

So what did I do wrong here ?! I followed the guide step by step (https://github.com/ansible/awx-operator) but still failed.

AH. I checked and found this open issue: https://github.com/ansible/awx-operator/issues/1391

Please see the releases pages for more details: AWX, Operator.

awx has an operator - https://github.com/ansible/awx-operator

I'm now attempting a POC to use k8s, despite having limited experience with it. I've successfully deployed AWX using the https://github.com/ansible/awx-operator on k8s, which includes Postgres. However, I'm unsure how to configure AWX with the plays that we publish in our CI/CD pipeline.

You can look at the operator source code https://github.com/ansible/awx-operator to see exactly what it does.

I have setup AWX Operator from https://github.com/ansible/awx-operator and everything works ok. But there's an annoying warning when running modules from the community.vmware collection.

We're happy to announce that AWX version 21.10.2 is now available! We're happy to announce that AWX Operator version 1.1.3 is now available! This AWX version downgrades a dependency which was causing tracebacks to appear often in the logs of some deployments.

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)