CloudHub 2.0 Release Notes

When you create a private space, you can now specify reserved CIDR blocks to connect your cloud or on-premises corporate network without a risk of IP address overlap.

Customers using the new pricing and packaging model can now leverage CPU-based horizontal autoscaling on CloudHub 2.0.

You can now enable trace data collection for applications using Mule Runtime 4.6 deployed to either shared or private spaces to leverage trace data export through Anypoint Monitoring Telemetry Exporter.

You can now opt into private-space infrastructure upgrade earlier than the scheduled patching process.

You can now configure application-level egress control rules.

For the 0.1 vCore offering in CloudHub 2.0, heap memory is now 480 MB.

When you attempt to delete a private space that has apps deployed, a warning appears, confirming you want to delete the private space and the apps that are deployed to it. If you continue to deletion, the private space and all its deployed apps are deleted.

You can now configure private space inbound firewall rules to manage TCP-based traffic. You can then use the Application Manager API to deploy apps using TCP ports.

For sizing replicas, the 0.1 vCore memory offering has been increased from 1 GB to 1.2 GB.

The application size limit for uploading and deploying CloudHub 2.0 apps through the Runtime Manager UI has increased from 200 MB to 350 MB.

The number of application properties you can configure has increased from 100 to 300. You can view these properties in the Settings section of your application.

CloudHub 2.0 now supports the deployment of API Gateways.

The limit for inbound and outbound firewall rules in a private space has increased from 40 to 180.

The limit for HTTP header length (maxHeaderLength) has increased from 16K to 32K.

You can now enable VPN logs to be directly accessible by MuleSoft support engineers. This shortens the process for obtaining the logs from AWS. For more information, see Enable VPN Logs.

When you configure a new private space, you can now remove the default route from the routing table.

Limits for vCores, VPCs, and networking connections across CloudHub and CloudHub 2.0 are now enforced at the organization level. Running applications are not impacted, but you must keep your applications in compliance to ensure all operations run smoothly. For more information, see Organization Entitlements.

You can now use queries to search application logs in Runtime Manager.

The Create VPN Connection > Advanced Options UI has changed.

The Log Points and Reports features in Anypoint Monitoring are now supported for CloudHub 2.0.

Application endpoints now support path rewrite. The Path Rewrite feature is available only for apps deployed in private spaces.

Get started fast
Set up an environment quickly with simplified configuration for private spaces and network connectivity.

Streamline your operations
Reduce management overhead with new auto-provisioning and auto-scaling ingress and load balancer in private spaces.

Take advantage of lightweight isolation
Improve performance and scale quickly with lightweight container-based application isolation.

Implement tighter security controls
Simplify static IP management and customize outbound firewall rules at the private space level.

Meet present and future needs, faster
Take advantage of new products and features faster to accelerate growth and innovation.