Tuesday, November 29, 2022

Sunsetting Bitnami Launchpads

Authored by Alejandro Gómez, R&D Manager at VMware

The Bitnami Launchpad service was released at the beginning of 2013, when the major cloud service providers—AWS, Azure, and Google—were just developing and launching application marketplaces for their platforms. Bitnami Launchpad offered a simpler user experience to deploy applications in the cloud. Providing our own service also allowed us to give users access to the latest, most up-to-date version faster than was available through the cloud vendor marketplaces. Thousands of applications have been deployed through the Bitnami Launchpad.

However, since those early days, cloud service providers have shortened their validation and publishing timelines, and the user experience for deployment from their marketplaces has improved considerably. Through these cloud platform marketplaces, users not only get a simplified process for procuring software, but now they also get faster access to the most recent version of Bitnami solutions as well as a fully integrated deployment experience with the platform of their choice.

In this context, today we are announcing the deprecation of the Bitnami Launchpad service and recommend deploying our solutions directly through the cloud service providers’ marketplaces. Here are answers to a few questions you might have.

Where can I find Bitnami by VMware solutions?
We have worked with the major cloud service providers to make our software available to you:

How does the Bitnami Launchpad deprecation affect my servers?
Your instances will not be stopped or removed because they are running in the platform of your choice under your cloud account. However, you will not be able to launch new servers or manage and access existing servers through the Bitnami Launchpad interface.

December 15, 2022: Launchpads will be accessible, but you will not be able to launch new instances or add new cloud credentials. However, you will still be able to manage your instances from our launchpads as well as from each cloud console.

February 15, 2023: Launchpads will no longer be accessible and you will have to manage your instances from each cloud console.

Which actions do I need to perform?
Option A (recommended): Upgrade your server. Launch a server for the most recent version of the application through one of our partners and migrate your data.

Option B: Ensure access to your existing server through the cloud service provider console. Download your SSH keys from the launchpads to ensure you will be able to access your instances after January 31, 2023. Find information about how to download them for each cloud provider:

Wednesday, November 9, 2022

Focusing on Cloud Native Solutions

Authored by Alejandro Gómez, R&D Manager at VMware

Since announcing our vision of focusing on cloud native solutions, we have remained fully committed and have put in a great deal of effort toward this goal. This is reflected in some of our recent updates, such as unifying the source of truth of the containers, conducting an analysis of our catalog size, and improving the container catalog size.

Today, we are announcing that Bitnami will discontinue the support for all native installers by November 30, 2022. This means that we will stop supporting native installers for OS X, Windows, and Linux.

We would like to reiterate our commitment to continuously improving our Cloud Images, VMs, containers, and Helm charts catalog and to helping the community. To that end, we recently added ClickHouse, KSQL, and Schema-registry to the catalog, and we continue to work on adding more solutions. As our catalog continues to be adopted by an increasing number of users, we strive to provide them with an excellent service by offering secure, well-configured, and up-to-date container images.

If you are a user of the installers, we recommend that you explore and adopt other supported deployment options, such as:

Learn more

For more information and tutorials about using Bitnami containers and Helm charts in Kubernetes, visit the Bitnami documentation page.