chore: configure hpa behavior

[ravisingal]

No description provided.

[github-actions]

Test Results

366 tests  ±0   366 ✅ ±0   8s ⏱️ ±0s
 67 suites ±0     0 💤 ±0 
 67 files   ±0     0 ❌ ±0 

Results for commit b43b6e7. ± Comparison against base commit 77592de.

This pull request removes 17 and adds 2 tests. Note that renamed tests count towards both.

      long: 60
      string: "PT1M"
      valueType: LONG
      valueType: STRING
    alias: "numCalls"
    columnName: "SERVICE.numCalls"
    value {
    }
  columnIdentifier {
…

org.hypertrace.gateway.service.baseline.BaselineServiceImplTest ‑ [1] function: AVGRATE
arguments {
  columnIdentifier {
    columnName: "SERVICE.numCalls"
    alias: "numCalls"
  }
}
arguments {
  literal {
    value {
      valueType: STRING
      string: "PT1M"
    }
  }
}
alias: "numCalls"

org.hypertrace.gateway.service.baseline.BaselineServiceImplTest ‑ [2] function: AVGRATE
arguments {
  columnIdentifier {
    columnName: "SERVICE.numCalls"
    alias: "numCalls"
  }
}
arguments {
  literal {
    value {
      valueType: LONG
      long: 60
    }
  }
}
alias: "numCalls"

[satish-mittal]

@ravisingal In simple words, this scaleUp policy will add max 2 pods within any 60 sec (until it reaches maxReplicas) and scaleDown policy will remove min 1 pod within any 600 sec (until it reaches minReplicas) after looking at previous window of 600 seconds, right?