Silvestre Zabala

Hi @onsi, thank you very much for the super-quick fix! We were already able to update to the new version: https://github.com/cloudfoundry/app-autoscaler-release/pull/1034

Hi @slavapeshkin, I agree that this would be a nice new feature! Currently, we are not working on it. As always, PRs are welcome.

Here's the [link to the repo logs](https://app.renovatebot.com/dashboard#github/cloudfoundry/app-autoscaler-release), as I'm always searching for it.

This will be taken care by removing the `metricsserver` from the codebase

This was done with https://github.com/cloudfoundry/app-autoscaler-release/pull/2983

@KevinJCross : Yep, per node makes most sense.

I believe this has been already addressed.

The main commit is https://github.com/cloudfoundry/app-autoscaler-release/pull/2824/commits/84b078fd2d82e7e57ce684f244d4b9349979724c - the other changes are unrelated and could be split out to their own PRs if necessary.

Hi @alibowl , the `cpu` metric is processed in https://github.com/cloudfoundry/app-autoscaler/blob/develop/src/autoscaler/metricsserver/collector/envelope_processor.go#L127 This means the App Autoscaler uses `CpuPercentage` as described in https://docs.cloudfoundry.org/loggregator/container-metrics.html#container-metrics (c.f. https://github.com/cloudfoundry/diego-logging-client/blob/master/client.go#L218 for the `CpuPercentage` to `cpu` mapping). I'd...

Hi @benjaminguttmann-avtq , the route is set in https://github.com/cloudfoundry/app-autoscaler-release/blame/912cbd185e60e5099342d723d5a242dbb07d5451/templates/app-autoscaler.yml#L296 and the line is there since the start of this file. I see that the old (deleted) deployment manifest did hardcode...