Skip to content

Releases: cloudfoundry/app-autoscaler-release

3.1.0

23 Aug 08:31
8b52511
Compare
Choose a tag to compare

Changelog for app-autoscaler-release

Enhancements

Bug Fixes

Chores

Dependency Updates

Read more

App Autoscaler v3.0.1

27 May 12:13
Compare
Choose a tag to compare

Change logs:

  • Support MySQL database now.
  • Security Fix : support TLSv1.2 and disable TLSv1.1 and TLSv1.0 for scheduler component. #237
  • Bug fix to resolve that schedules can not removed in synchronization when an application was deleted.
  • MetricsCollector: Only process HTTPStartStopEvents with peerType client

Please note that app autoscaler using cf deployment database is blocked by the PR cf-deployment #881.

If you would like to use database of cf deployment, you should create a database named autoscaler manually or when deploy cf deployment, please apply with the ops file operations/experimental/set-autoscaler-db.yml.
Please refer to README for details.

App Autoscaler v3.0.0

08 Nov 06:12
37f28f8
Compare
Choose a tag to compare

Major changes includes in this release :

Custom metric support is open on Cloud Foundry App-Autoscaler Now !

Please refer to Custom metric usage guide for details !

Starting from 3.0.0, you need to use https://github.com/cloudfoundry/app-autoscaler-release/blob/master/templates/app-autoscaler-deployment.yml only. The previous -v1 version won't work anymore.

App Autoscaler v1.2.4

24 Sep 08:47
c31a2ae
Compare
Choose a tag to compare
App Autoscaler v1.2.4 Pre-release
Pre-release

This is a hotfix based on App Autoscaler v1.2.3 to rollback the failure transition of "saving metrics".

App Autoscaler v1.2.3

29 Aug 05:31
52d085d
Compare
Choose a tag to compare
App Autoscaler v1.2.3 Pre-release
Pre-release

This is a hotfix based on App Autoscaler v1.2.2, which includes a fix to resolve the Liquibase staled db lock issue which may prevent autoscaler jobs from starting.

App Autoscaler v2.0.0

15 Aug 04:29
4407aa7
Compare
Choose a tag to compare

Major changes includes in this release :

Adapt to loggregator v2 API to stream multiple application metrics in parallel. To achieve this, the metric collector component is replaced by metric server and metric gateway components.

To use the latest feature, you can deploy with the default template/app-autoscaler-deployment.yml. The cf deployment variables need to be provided as well.

If you would like to continue to use the previous metric collector component along with loggregator V1 API, you can deploy with templates/app-autoscaler-deployment-v1.yml or templates/app-autoscaler-deployment-fewer-v1.yml.

Refer to the README for details.

App Autoscaler v1.2.2

19 Jun 04:41
Compare
Choose a tag to compare
  • Change to UAA token endpoint for client id validation.

App Autoscaler v1.2.1

24 Apr 05:39
5e3d788
Compare
Choose a tag to compare

Major changes since v1.1.0

  • Add caching of app metrics in event generator
  • Add support for not persisting instance metric into Postgres SQLDB.
  • Enhance health endpoint using Prometheus instrumentation for API server
  • Enable https/TLS support when connecting to Postgres SQLDB

The v1.2.1 version includes an important fix to enable https/TLS support when connecting to Postgres SQLDB on all components.

Please refer to our Readme file to check how to "Deploy autoscaler with postgres database enabled TLS" with bosh deployment. By default, the support Postgres SSL mode is "verify_full" with a valid CA.

App Autoscaler v1.2.0

10 Apr 08:57
5d23816
Compare
Choose a tag to compare
App Autoscaler v1.2.0 Pre-release
Pre-release

Change logs

  • Add caching of app metrics in event generator
  • Add support for not persisting instance metric into Postgres SQLDB.
  • Enhance health endpoint using Prometheus instrumentation for API server
  • Enable https/TLS support when connecting to Postgres SQLDB (except API server)

App Autoscaler v1.1.0

20 Dec 18:26
0a4ef0f
Compare
Choose a tag to compare

Change logs

  • Allow cf admin to be able to manage scaling policies, query metrics and events besides space developer
  • Add CPU based scaling( Provided AS-IS, see discussions here for CPU based scaling issues https://docs.google.com/document/d/16TvBsZSInjy7zoboSQWRJo30lmxr07tvd40_GzpfD3I)
  • Add health endpoint for each components using Prometheus instrumentation
  • Add caching of instance metrics in metrics collector