The TriggerMesh Cloud Native Integration Platform consists of a set of APIs which allows you to build event-driven applications. Implemented as a set of Kubernetes CRDs and a Kubernetes controller, it gives you a way to declaratively define your event sources and event targets, in addition to potential actions needed in your applications: content-based event filtering, event splitting, event transformation and event processing via functions.
To install TriggerMesh, follow the installation instructions.
Register TriggerMesh APIs by deploying the Custom Resources Definitions:
kubectl apply -f https://github.com/triggermesh/triggermesh/releases/latest/download/triggermesh-crds.yamlDeploy the platform:
kubectl apply -f https://github.com/triggermesh/triggermesh/releases/latest/download/triggermesh.yamlBy default, TriggerMesh works with resources across all namespaces in the Kubernetes cluster. This requires permissions provided by ClusterRoles and ClusterRoleBindings. If cluster-wide permissions are not desired, TriggerMesh can be configured to run in a single namespace. To get the namespace-scoped installation, first, deploy the CRDs:
kubectl apply -f https://github.com/triggermesh/triggermesh/releases/latest/download/triggermesh-crds.yamlAnd then, using kubectl's "kustomization" feature, install customized manifests:
kubectl apply -k config/kustomization/namespaced/Controllers created with this command won't reconcile resources outside the triggermesh namespace, ClusterRoleBindings will have the namespace scope.
Please refer to our guidelines for contributors.
TriggerMesh Inc. offers commercial support for the TriggerMesh platform. Email us at [email protected] to get more details.
This software is licensed under the Apache License, Version 2.0.
Additionally, the End User License Agreement included in the EULA.pdf file applies to compiled
executables and container images released by TriggerMesh Inc.