Hello everyone,
After installing the awx-operator using Helm in Kubernetes, can I remove the “aww-operator-controller-manager” deployment or scale the associated pods to 0 without causing any issues to the remaining AWX instance? In our test setup, this seems to work without any problems, and the AWX application continues to run stably. The awx-operator would then be reinstalled when an update is needed, i.e., during a “helm upgrade”. And then removed again.
This would have the advantage of not having the images of the awx-operator-controller-manager and kube-rbac-proxy in a productive Kubernetes environment in the meantime, and we would not have to worry as much about the security vulnerabilities in these images.
Or have I overlooked something that requires the operator to run continuously after installation? Or are there tasks that the operator urgently needs to perform during ongoing operations?
It would be great if someone could provide an assessment of this. Thank you in advance!"