Note in ECK autoscaling docs how cpu/ram is scaled. (#1029)

From the existing ECK docs, it sounds as though CPU and Ram can be
independently scaled with a "Decider" from Elasticsearch, but no such
decider exists. This makes it clear that cpu/ram are scaled relative to
the storage min/max settings.

---------

Signed-off-by: Michael Montgomery <[email protected]>
Co-authored-by: Peter Brachwitz <[email protected]>

Author: naemono

deploy-manage/autoscaling/autoscaling-in-eck.md

@@ -20,6 +20,14 @@ Configure autoscaling for {{es}} deployments in {{eck}}. Learn how to enable aut
 
 ECK can leverage the [autoscaling API](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-autoscaling) introduced in {{es}} 7.11 to adjust automatically the number of Pods and the allocated resources in a tier. Currently, autoscaling is supported for {{es}} [data tiers](/manage-data/lifecycle/data-tiers.md) and machine learning nodes.
 
+### Supported Resources for Autoscaling per Elasticsearch Tier
+
+| Tiers | Storage | Memory | CPU |
+| --- | ---| --- | --- |
+| Data Nodes (except Frozen) | Yes | Calculated proportionally to the required amount of storage | Calculated proportionally to the required amount of memory
+| Frozen Nodes | Yes | Yes | Calculated proportionally to the required amount of memory
+| Machine Learning | No | Yes | Calculated proportionally to the required amount of memory
+
 
 ### Enable autoscaling [k8s-enable]
 
@@ -345,4 +353,4 @@ spec:
         target:
           type: Utilization
           averageUtilization: 50
-```
+```