W-14455221-rtm-autoscaling

[luanamulesoft]

Writer's Quality Checklist

Before merging your PR, did you:

• Run spell checker
• Run link checker to check for broken xrefs
• Check for orphan files
• Perform a local build and do a final visual check of your content, including checking for:
  • Broken images
  • Dead links
  • Correct rendering of partials if they are used in your content
  • Formatting issues, such as:
    • Misnumbered ordered lists (steps) or incorrectly nested unordered lists
    • Messed up tables
    • Proper indentation
    • Correct header levels
• Receive final review and signoff from:
  • Technical SME
  • Product Manager
  • Editor or peer reviewer
  • Reporter, if this content is in response to a reported issue (internal or external feedback)
• If applicable, verify that the software actually got released

[rithishapadmanabh]

I would change the organization of this section.

1. The title can be CPU based Horizontal Autoscaling to be very specific about the feature we have.
2. The description of HPA is really the same for both CH2 and RTF. So I would move that to above the table, and in the table/as bullets just link out to specifically CH2 and RTF sections

• Horizontal autoscaling makes Mule applications deployed to CloudHub 2.0 and RTF responsive to CPU usage by automatically scaling up or down replica capacity as needed. In Kubernetes, a Horizontal Pod Autoscaler (HPA) automatically updates a workload resource to automatically match demand.

[rithishapadmanabh]

Slightly misleading - customers may perceive that they can configure signals. But reality is Mulesoft configures signals (70% etc) out of the box so it is not controllable by the customer, and the only signal we support is CPU, so customers cannot configure type of signal either.

[rithishapadmanabh]

I'd change to in response to CPU usage the application

[luanamulesoft]

I added the same text for both CH2 and RTF, but maintained in separate rows, to respect the structure of the page.