In a previous post, we described how we envision cloud-native initiatives reaching the 2.0 phase, where phase 1 was centered around providing clusters and running its underlying infrastructure effectively. Now that teams are starting to move some of their existing services to a microservices architecture, developers and platform engineers are being tasked with implementing the right policies and governance controls to ensure applications are running as securely as possible.

It has been 6 months since our engineering team started to work on what we decided to call Qovery v2. But what makes this next release so cool? Here are the top 4 features that make this release so appealing.

Microsoft recently reported two widespread cryptomining attacks targeting Kubeflow, a popular cloud-native platform for machine learning (ML) workloads on Kubernetes. Attackers targeted Kubeflow installations using either the Kubeflow central dashboard interface or Kubeflow Pipelines interface for scheduling crypto-mining workloads.

Three months ago, we launched VMWare Tanzu RabbitMQ for Kubernetes to automate high-performance messaging on demand with our cluster Operator.* Since then, customers have approached us with higher-level needs that inspired us to extend and improve Tanzu RabbitMQ. In other words, you’ve spoken, and we’ve listened. And so now, in version 1.1, we go well beyond automating cluster operations to orchestrating complex topologies, adding alerts, and previewing active-passive replication.

We’re happy to debut our new website, highlighting our newest features! We’ve been busy updating our product UI and decided to showcase some of the work on the site. All of our case studies, whitepapers, and datasheets are now in the Resources page. We’ve also been featured on a variety of news sites, podcasts and blogs. We linked all of them in the “Speedscale in the Media” section.