Hybrid Multicloud Serverless on Red Hat OpenShift
This week we are announcing that the TriggerMesh operator is available for Red Hat OpenShift. An Operator is a method of packaging, deploying and managing a Kubernetes-native application. A Kubernetes-native application is an application that is both deployed on Kubernetes and managed using the Kubernetes APIs and kubectl tooling. But that’s what it is, what’s more interesting, is what TriggerMesh can do for OpenShift users. The TriggerMesh OpenShift operator is open source and can be found on GitHub.
By enabling users to deploy TriggerMesh on OpenShift it allows them to manage all their serverless infrastructure consistently across all clouds. The automation and cross-cloud event capabilities provide a mechanism to create cloud native architectures that are cross-cloud. TriggerMesh on OpenShift helps enable the hybrid multicloud visions of Red Hat.
In the early days of cloud computing, the implication of hybrid cloud was that workloads would be moving from one cloud to another. In the world of microservices and serverless we believe that it’s likely that serverless functions will reside on many clouds; Google, Microsoft, Amazon, and your own data center. You will host and trigger functions through events happening across cloud silos. TriggerMesh provides a way to deploy your functions to the cloud of your choice or Knative-enabled Kubernetes functions. In addition, you can use event sources from one cloud to another or from your legacy applications to public clouds like Amazon Lambda, Google Cloud Functions, and now OpenShift.
For example, you may want to trigger a function running on Red Hat OpenShift when a file is uploaded to Amazon S3. You may need to trigger a function on Knative-Kubernetes from Apache Kafka or another messaging technology like Google’s PubSub. These are the kinds of things TriggerMesh can make happen for your event-driven cloud native applications.
Partnering with Red Hat hat and VSHN
We are very happy to have the opportunity to work with Red Hat and VSHN to deliver TriggerMesh capabilities to OpenShift users.
“The Operators available in OpenShift 4 could drastically change the way people manage applications,” according to VSHN CTO Aarno Aukia. “TriggerMesh with its powerful interface promises to ease the adoption of serverless workload through Knative and Tekton.”
“We are excited to work with TriggerMesh as they bring their Kubernetes Operator to the broader Kubernetes community,” said Julio Tapia, director, Cloud Platforms Partner Ecosystem, Red Hat. “Operators help in building business logic to create and automate the lifecycle of a Kubernetes-native application, making day-to-day operations easier. As part of the Operator community, by leveraging the OpenShift Serverless Operator capabilities available in OpenShift 4 through Knative, TriggerMesh is helping to drive innovation around Kubernetes-native infrastructure and across the hybrid cloud.”
TriggerMesh for Multicloud Hybrid Serverless
TriggerMesh wants to help you integrate technology across all your infrastructure in your data center and public clouds. As your cloud native applications grow it’s likely they will be made up of serverless functions running across multiple clouds. Having a consistent way to deploy your serverless functions and to trigger them will be a growing consideration as you continue to adopt serverless technologies and cloud native applications. TriggerMesh’s hybrid serverless solutions can be a considerably useful tool for maximizing your serverless productivity. If you would like to try TriggerMesh and host serverless functions for free you can sign-up for a free account today.