k8s-mediaserver-operator VS awx-operator

I'm having an issue with this, and I'm hoping someone can help. I am relatively new to Kubernetes, and to concepts such as custom resource definitions. I am trying to set up kubealex/k8s-mediaserver-operator, which first has you create a CRD via one YML file, and then apply a second file which should then use the CRD to actually create all of the objects.

https://github.com/kubealex/k8s-mediaserver-operator/blob/2e5b9e36f605f76789191303f9697bd15d4d7dd1/helm-charts/k8s-mediaserver/templates/radarr-deployment.yaml#L55

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.