What's New

Bluemix Cloud Foundry: Diego is live

Share this post:

cloudfoundry_heroUpdated: 2/3/2017 (including new “auto-migrate” button)

IBM Bluemix has reached a great milestone with the Bluemix Cloud Foundry upgrade to Diego architecture. We talked about it in this previous blog, and now the next phase is complete. The reasons for this update are numerous and the benefits are significant.

Upgrade Complete

Upgrading the world’s largest Cloud Foundry platform had to be done with care and forethought, and many people in IBM Bluemix made it happen. Our team transitioned all the public environments to Diego and made that the default deployment target, so new apps that are pushed will deploy to a Diego cell. Existing apps deployed to the DEA architecture are still available on their DEA homes, but only for a little while longer. The DEA architecture will soon be sunset and removed, leaving Diego the singular path forward.

While applications can usually run as-is, they do need to be migrated to the new architecture. IBM will do it for app owners, but we’d rather they do it themselves and ensure everything is working as expected in their continual delivery processes. End-of-January was the self-migration target and we’re now in the IBM-initiated migration phase.

Bluemix Console Updates

To help you with the transition, we’ve made some changes to the Bluemix user interface to make it clear which apps still need to move to Diego.

If you have Cloud Foundry applications not yet migrated to Diego, you’ll get a reminder when you log in.


We’ve followed up with a smaller reminder at the top of the Cloud Foundry application list page.

We’ve decorated the applications list with a reminder and label to show which applications are still running on the older DEA architecture and included a link to tell you how to migrate.


Updated: The Migrate to Diego button is now capable of auto-migrating your application to Diego, and rolling it back if necessary. So it’s nice and simple with one click!

And we’ve repeated that information on the application-specific detail page.



These helpful messages should notify you which applications still need to be migrated to Diego in the Bluemix Public zones.

Next Steps

Once your Public Bluemix Cloud Foundry applications have been migrated to Diego and are working successfully, you’re done.

Bluemix Dedicated and Local migration plans are under way; those will be transitioned in the coming weeks with individual customers.

For information about migrating your applications, please see Application Deployment.

For everything you need to know about managing Cloud Foundry apps in Bluemix please see IBM Bluemix Cloud Foundry Managing Apps documentation.

IBM Cloud Offering Manager

More What's New stories
May 2, 2019

Seamless Integration: Istio and External Services

By defining our own MCP server, we allow users to move to the Istio service mesh without any code and deployment model changes. This means we can easily use Istio to control, observe, connect, and secure services running outside Kubernetes clusters.

Continue reading

April 26, 2019

Help Shape the Future of Cloud Foundry

Are you a Cloud Foundry user? If so, here's your opportunity to influence the future of Cloud Foundry with the 2019 user survey.

Continue reading

April 25, 2019

Java Licensing Has Changed, but There’s Good News

If you downloaded your Java SE binary from Oracle.com and are using it for commercial purposes, you have probably heard that they’ve introduced a new pricing model. Fortunately, the Eclipse OpenJ9 project delivers a no-cost JVM on AdoptOpenJDK, even for commercial use. As an added bonus, OpenJ9 is faster and leaner than other JVMs.

Continue reading