search

ansible / awx-operator

An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
https://www.github.com/ansible/awx
Apache License 2.0
1.24k stars 628 forks source link

Add functionality to AWX Operator to install Plugins into AWX (specifically Credential plugins) #1335

Open bar0n36 opened 1 year ago

bar0n36 commented 1 year ago

Please confirm the following

Feature Summary

Historically, you could install credential plugins directly into the running AWX instances (and by docker-compose) as per https://github.com/ansible/awx-custom-credential-plugin-example

There does not appear to be a way to install plugins into AWX as deployed by the AWX Operator, as there appears to be no functionality (or there is no documentation) as to how to get the AWX Operator to deploy these plugins into an AWX instance. In my particular case, I have developed a credential plugin for an additional credential store platform, that I have successfully running on my development docker deployment without issue, but I have been unable to find a way to deploy it into a live AWX instance deployed via Operator.

Can this functionality please be added to AWX Operator, or if it is already there, the documentation be updated (or me pointed in the direction, as I am yet to receive a response to my mailing list post - admittedly only a couple of days, but I am pretty sure the functionality doesn't exist)

Thanks.

lknite commented 1 year ago

Yes please, OIDC is much preferred over LDAP.

When deploying via gitops using argocd/flux and similar, I'd like to configure OIDC. This would require installing the oidc related plugin & somehow also providing the configuration via values.yaml so immediately upon deployment it is possible to login.

like this: https://josh-tracy.github.io/Ansible_Tower_RedHatSSO/

bar0n36 commented 1 year ago

Feedback from the mailing list is currently 'build a custom image with the plugin baked in'. While this is feasible, it defeats what I would think is the purpose of a 'plugin' if I have to build a whole new image to deploy it. Would be much better if this functionality was included (if possible) in the Operator.