Skip to content

Commit

Permalink
cpu/mem scalers can scale to zero (kedacore#1088)
Browse files Browse the repository at this point in the history
Signed-off-by: gauron99 <[email protected]>
Signed-off-by: David Fridrich <[email protected]>
Co-authored-by: Zbynek Roubalik <[email protected]>
  • Loading branch information
gauron99 and zroubalik authored Mar 17, 2023
1 parent 52de60a commit fff3e34
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion content/docs/2.11/scalers/cpu.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ go_file = "cpu_memory_scaler"

> **Notice:**
> - This scaler **requires prerequisites**. See the 'Prerequisites' section.
> - This scaler will never scale to 0 and even when user defines multiple scaler types (eg. Kafka + cpu/memory, or Prometheus + cpu/memory), the deployment will never scale to 0.
> - This scaler can scale to 0 only when user defines at least one additional scaler which is not CPU or Memory (eg. Kafka + CPU, or Prometheus + CPU) and `minReplicaCount` is 0.
> - This scaler only applies to ScaledObject, not to Scaling Jobs.
### Prerequisites
Expand Down
2 changes: 1 addition & 1 deletion content/docs/2.11/scalers/memory.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ go_file = "cpu_memory_scaler"

> **Notice:**
> - This scaler **requires prerequisites**. See the 'Prerequisites' section.
> - This scaler will never scale to 0 and even when user defines multiple scaler types (eg. Kafka + cpu/memory, or Prometheus + cpu/memory), the deployment will never scale to 0.
> - This scaler can scale to 0 only when user defines at least one additional scaler which is not CPU or Memory (eg. Kafka + Memory, or Prometheus + Memory) and `minReplicaCount` is 0.
> - This scaler only applies to ScaledObject, not to Scaling Jobs.
### Prerequisites
Expand Down

0 comments on commit fff3e34

Please sign in to comment.