-
Notifications
You must be signed in to change notification settings - Fork 591
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
Resources for migration-job. #1841
Comments
Have you tried setting a LimitRange?
That would ensure that every pod has pre-defined resources without overwriting existing resource specifications. |
Yes, this is what has been done. But i'm not a cluster admin. Cluster was prepared by our K8S admins, we have limited access to configuration and also custom permissions to install operator. |
I see. If I am not mistaken there is a ResourceQuota on the namespace you are working on. Adding resources to the migration job is a good solution and I hope it is implemented, but there are also other pods (like the ones running AWX jobs) that will also have the same error. The LimitRange solution has been working in my case. |
As i mentioned before, limitRange was already set on my cluster. About running jobs, isn't this setting ee_resource_requirements responsible for assigning resources to running execution environments? |
I thought so as well, but it did not work for me. However, I found out it can also be defined in the WebUI. |
Could you guide me where did you found thoses settings? |
@norbertgrz, I ran into the same issue as you and stumbled upon this thread. I think @JMora77 means something along the lines of this which worked for me:
|
Also not sure if this page is of any use: https://ansible.readthedocs.io/projects/awx-operator/en/latest/user-guide/advanced-configuration/containers-resource-requirements.html |
This is set already, but it is only workaround for me. I have no cluster admin permissions, so controlling limitRange is out of my scope. |
Please confirm the following
Feature Summary
As we are working on namespaces with quota limitations on our kubernetes cluster, we are unable to deploy awx-operator. Migration job created by operator has no resources specified and this is why pod is not created.
Is there a posibility to add resources to migration job template?
The text was updated successfully, but these errors were encountered: