Files
awx-operator/docs/user-guide/advanced-configuration/scaling-the-web-and-task-pods-independently.md
kurokobo 2b0221bbc6 docs: overall minor renovations (#1874)
* docs: simplify README.md and make index.md to refer to it
* docs: change order for pages in navigation and add missing pages
* docs: fix headings to improve navigation, transform notes to admonition, fix indentation, linting issues and minor issues
* docs: merge docs for using images from private registries
* docs: add example to integrate LDAP configuration via extra_settings_files
* Apply suggestions from code review
docs: apply suggested changes

Co-authored-by: Don Naro <dnaro@redhat.com>

* docs: update the doc site url as same as the url in https://www.ansible.com/ecosystem/
* docs: minor fixes for hpa page
* docs: expand note block
* docs: apply #1904 to README.md

---------

Co-authored-by: Don Naro <dnaro@redhat.com>
2024-07-20 18:34:21 -04:00

1.0 KiB

Scaling the Web and Task Pods independently

You can scale replicas up or down for each deployment by using the web_replicas or task_replicas respectively. You can scale all pods across both deployments by using replicas as well. The logic behind these CRD keys acts as such:

  • If you specify the replicas field, the key passed will scale both the web and task replicas to the same number.
  • If web_replicas or task_replicas is ever passed, it will override the existing replicas field on the specific deployment with the new key value.

These new replicas can be constrained in a similar manner to previous single deployments by appending the particular deployment name in front of the constraint used. More about those new constraints can be found in the Assigning AWX pods to specific nodes page.

Horizontal Pod Autoscaling

The operator is capable of working with Kubernetes' HPA capabilities. See Horizontal Pod Autoscaler documentation for more information.