CAPI 1.138.0
Highlights
This release contains two experimental features:
Deploying Cloud Controller using Puma (instead of Thin) is now possible via a configuration option
For now, this is intended for performance testing and not for production use. Please beware that Cloud Controller metrics have not been adapted to account for multiple workers on a single VM, and will behave unpredictably when using Puma as a server.
Deploying all Cloud Controller ruby jobs with the experimental Ruby YJIT compiler is also available via a configuration option. This feature may improve performance at the expense of memory usage. This is also not recommended for production use.
CC API Version: 2.191.0 and 3.126.0
Service Broker API Version: 2.15
CAPI Release
Add experimental option to use Puma instead of Thin: #269
Add experimental option to enable Ruby YJIT compiler: #270
Cloud Controller
Make route destinations ordering consistent cloudfoundry/cloud_controller_ng#2861
Fix service instance operations duplicates root cause cloudfoundry/cloud_controller_ng#2916
Print RUBY_DESCRIPTION to stdout on startup cloudfoundry/cloud_controller_ng#2966
Enable opting for Puma webserver instead of Thin: cloudfoundry/cloud_controller_ng#2965
Cloud Controller Database Migrations
None
Dependency bumps:
bump fog-aws from 3.14.0 to 3.15.0
Full Changelog: 1.137.0...1.138.0