Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ExternalSecret for Ansible AWX сredentials and URL #285

Open
daniil-nedostup opened this issue Aug 27, 2024 · 0 comments · May be fixed by #286
Open

Add ExternalSecret for Ansible AWX сredentials and URL #285

daniil-nedostup opened this issue Aug 27, 2024 · 0 comments · May be fixed by #286
Assignees
Labels
enhancement New feature or request

Comments

@daniil-nedostup
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Currently, there is no external secret in the repository that holds the credentials and URL for Ansible AWX. This makes it challenging to securely manage and access the necessary information for AWX when it is deployed in a different namespace. Without a centralized secret, credentials may be duplicated or inconsistently managed across the platform.

Describe the solution you'd like
Add an ExternalSecret to the repository that contains fields for the Ansible AWX admin user's username, password, and the url pointing to the AWX instance. This secret should be designed to pull the necessary data from a secure location, ensuring that all required information for AWX is stored and managed centrally. This will allow different components of the platform to access the AWX credentials securely and consistently, even if AWX is deployed in a different namespace.

Describe alternatives you've considered
An alternative could be to manually manage AWX credentials within each namespace where they are needed, but this approach risks inconsistencies and potential security issues due to credential duplication. Another alternative is to use environment variables, but this does not provide the same level of security and centralized management as an ExternalSecret.

Additional context
By adding an ExternalSecret, platform deployment and management will be simplified, as the necessary AWX credentials will be easily accessible and securely stored. This approach aligns with best practices for managing secrets and ensures that AWX can be effectively integrated into the platform, regardless of namespace boundaries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

1 participant