Unable to modify resource requests/limits for pods (e.g., Automation Hub) when Ansible Automation Platform is installed using the Operator
Issue
- Unable to update existing values for resource requests and limits in the Automation Hub pod after installation;
- When a new environment is deployed the requests/limits are applied correctly, however, any subsequent changes made to these values in the Ansible Automation Platform CR are not reflected in the respective component CRs.
- Changes made to the Ansible Automation Platform CR are not propagated as the Automation Hub CR remains unchanged.
Environment
- Red Hat Ansible Automation Platform (Ansible Automation Platform) 2.5, 2.6
- Ansible Automation Platform installation via Operator;
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.