Christian Adams

@miles-w-3 thanks for the patch. I cherry-picked it to my fork's devel and tried to stage and promote a release there with both of our changes: * https://github.com/ansible/awx-operator/pull/1013 * https://github.com/ansible/awx-operator/pull/1008...

Thanks for the tip @miles-w-3 , that did the trick. See https://github.com/ansible/awx-operator/pull/1013 comments, I think we are ready to merge unless you have any reasons to hold off.

Today's release used the PR associated with this issue and was successful. AWX Operator v0.26.0 is now available!

I just merged [this PR](https://github.com/ansible/awx-operator/pull/1001) to upgrade the operator-sdk to v1.22.0 so that we can bump the ansible-operator base image and clear up most of these security scan vulnerabilities. There...

@blackluck The tricky part about making it configurable for `make deploy` or `kustomize` style operator deployments is that it would require Role and RoleBinding to be changed to ClusterRole and...

Yes, @kdelee is right. These 3 conditions in the molecule test linked above (which CI runs) will not be met until the readiness probe is successful. The probe will not...

@moonrail I agree with your idea to run the migrations in an initContainer, I think that is a great approach. FYI, the CI failure was resource related and was fixed...

@kirillmandrygin Support for specifying the ingress and route api_version was added by this PR here: * https://github.com/ansible/awx-operator/pull/1098 Though unfortunately, it seems that we forgot to update the docs with that...

We don't have any "platform" tags or variables to key off of, and I think we should avoid adding too much platform specific logic to the awx-operator if possible. After...

Apologies for the wait on this one. Thank you for the contribution!