Ready for Cloud Native 2.0? 3 DevOps Strategies for the Next Era in Cloud Native

Bruno Andrade, CEO

Bruno Andrade is the CEO at, a cloud native application management framework to manage the full application lifecycle. Previously, he has held engineering leadership roles at Juniper Networks, Oracle, and IBM, and was the CEO of HTBASE. He lives in Mountain View, California.

After the rush to take advantage of cloud native application development and tools like Kubernetes, DevOps teams now have a lot more to think about. In many cases, DevOps adopted early continuous integration/continuous deployment (CI/CD) pipeline tools such as Jenkins, and are now attempting to apply them in cloud native scenarios where they aren’t the appropriate fit they once were. Cloud native pulls the developer down to infrastructure-related operations, and the current CD tools cannot help bring back the application-level context that developers once had before moving to a microservices architecture – hence, adding more complexity to the development workflow and observability of applications post-deployment. DevOps teams also face new challenges in application policy management, especially so in closely regulated industries, as they adapt their processes to establish trust and security in cloud native environments. At the same time, DevOps needs to reevaluate approaches to automation and strategies for eliminating human error, as cloud and Kubernetes deployments have ushered in a return of very manual and tedious efforts.

This session digs into details around three cloud native 2.0 strategies that DevOps teams ought to consider sooner than later to stay on top of a fast-changing ecosystem: 1) how to build CI/CD pipelines with greater interoperability and composability, 2) how and why to harness application policy management, and 3) how to balance automation and audits