To follow up. I have encountered more issues. I found that operator does not like Kubernetes version 1.23, I.22 works so that is an upgrade from what you have. In the awx-clb-without-tls.yaml file you need information about the ingress path as you have in the awx-ingress.yaml file, after creating and then destroying the CFT's multiple times, I got past the issues, I got an error for duplicate security groups, removed all lingering security groups. I had to add 2 tags to the subnets that I was using. I finally have the web address for the ingress, but it is not active. For someone that has no Kubernetes experience, I am learning alot now.

Looks like the PostGRES pod is not populated.

I see this NAME READY STATUS RESTARTS AGE pod/awx-operator-controller-manager-66877cf657-n9wj7 1/2 ImagePullBackOff 0 47m pod/awx-postgres-13-0 0/1 Pending 0 43m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/awx-operator-controller-manager-metrics-service ClusterIP 172.20.28.4 <none> 8443/TCP 47m service/awx-postgres-13 ClusterIP None <none> 5432/TCP 43m NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/awx-operator-controller-manager 0/1 1 0 47m NAME DESIRED CURRENT READY AGE replicaset.apps/awx-operator-controller-manager-66877cf657 1 1 0 47m NAME READY AGE statefulset.apps/awx-postgres-13 0/1 43m NAME TYPE DATA AGE secret/awx-admin-password Opaque 1 47m secret/awx-broadcast-websocket Opaque 1 43m secret/awx-operator-controller-manager-token-r8tcs kubernetes.io/service-account-token 3 47m secret/awx-postgres-configuration Opaque 6 47m secret/awx-secret-key Opaque 1 43m secret/default-token-wn5xk kubernetes.io/service-account-token 3 47m secret/redhat-operators-pull-secret Opaque 1 43m As you can see the PostGRES is pending doesn't go live.

I read down further and I figured out the error, I should have run the command twice, made two passes before running the clb with no SSL YAML file. But it hangs on the first pass at backupAWS... something I run the second pass and it never completes, it is like it doesn't get the DB created.

Thank you for this... I have worked in the past to get onto AWS EKS, this helps. I am having an issue though, I get the EKS build with nodes, but when I run the Kustomization towards the bottom I have an error: error: resource mapping not found for name: "awx" namespace: "awx" from ".": no matches for kind "AWX" in version "awx.ansible.com/v1beta1" ensure CRDs are installed first. The full output is this: kubectl apply -k . namespace/awx created customresourcedefinition.apiextensions.k8s.io/awxbackups.awx.ansible.com created customresourcedefinition.apiextensions.k8s.io/awxrestores.awx.ansible.com created customresourcedefinition.apiextensions.k8s.io/awxs.awx.ansible.com created serviceaccount/awx-operator-controller-manager created role.rbac.authorization.k8s.io/awx-operator-awx-manager-role created role.rbac.authorization.k8s.io/awx-operator-leader-election-role created clusterrole.rbac.authorization.k8s.io/awx-operator-metrics-reader created clusterrole.rbac.authorization.k8s.io/awx-operator-proxy-role created rolebinding.rbac.authorization.k8s.io/awx-operator-awx-manager-rolebinding created rolebinding.rbac.authorization.k8s.io/awx-operator-leader-election-rolebinding created clusterrolebinding.rbac.authorization.k8s.io/awx-operator-proxy-rolebinding created configmap/awx-operator-awx-manager-config created secret/awx-admin-password created secret/awx-postgres-configuration created service/awx-operator-controller-manager-metrics-service created deployment.apps/awx-operator-controller-manager created error: resource mapping not found for name: "awx" namespace: "awx" from ".": no matches for kind "AWX" in version "awx.ansible.com/v1beta1" ensure CRDs are installed first Can you assist with this? Thank you.