-
Notifications
You must be signed in to change notification settings - Fork 14
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 support for AWX installation via AWX Operator #122
Labels
enhancement
New feature or request
Comments
daniil-nedostup
added a commit
that referenced
this issue
Aug 19, 2024
10 tasks
daniil-nedostup
added a commit
that referenced
this issue
Aug 20, 2024
daniil-nedostup
added a commit
that referenced
this issue
Aug 22, 2024
daniil-nedostup
added a commit
that referenced
this issue
Aug 22, 2024
daniil-nedostup
added a commit
that referenced
this issue
Aug 23, 2024
MykolaMarusenko
pushed a commit
that referenced
this issue
Aug 23, 2024
github-project-automation
bot
moved this to Done
in KubeRocketCI (EPAM Delivery Platform)
Aug 23, 2024
daniil-nedostup
added a commit
that referenced
this issue
Aug 28, 2024
10 tasks
SergK
pushed a commit
that referenced
this issue
Aug 28, 2024
daniil-nedostup
added a commit
that referenced
this issue
Nov 11, 2024
11 tasks
MykolaMarusenko
pushed a commit
that referenced
this issue
Nov 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The current repository lacks the capability to deploy AWX using the AWX Operator. This limitation is inconvenient for users who prefer or require the operator-based approach for managing and scaling AWX deployments. Without this feature, users may need to manually set up and manage AWX, which could be error-prone and time-consuming.
Describe the solution you'd like
Implement the ability to deploy AWX via the AWX Operator within this repository. This would involve adding the necessary configurations, templates, and documentation to support an operator-based deployment, ensuring seamless integration and ease of use for users.
Describe alternatives you've considered
An alternative is to continue using manual AWX deployments without the operator, but this approach does not provide the same level of automation, scalability, and management capabilities that an operator-based deployment offers. Another option could be to deploy AWX through Helm charts, though this would also require additional setup and maintenance.
Additional context
Incorporating the AWX Operator into the deployment process could enhance the overall user experience by streamlining the installation and management of AWX instances. It would also align with best practices for deploying and managing Kubernetes-native applications.
The text was updated successfully, but these errors were encountered: