Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

https://github.com/triggermesh/triggermesh

TriggerMesh is the open-source AWS EventBridge alternative. It provides a unified eventing experience, a developer-friendly CLI, and runs on Docker or natively on Kubernetes.
https://github.com/triggermesh/triggermesh

cloudevents integration knative

Last synced: 18 days ago
JSON representation

TriggerMesh is the open-source AWS EventBridge alternative. It provides a unified eventing experience, a developer-friendly CLI, and runs on Docker or natively on Kubernetes.

Lists

README

        

![TriggerMesh Logo](.assets/triggermesh-logo.png)

[![Release](https://img.shields.io/github/v/release/triggermesh/triggermesh?label=release)](https://github.com/triggermesh/triggermesh/releases)
[![CircleCI](https://circleci.com/gh/triggermesh/triggermesh/tree/main.svg?style=shield)](https://circleci.com/gh/triggermesh/triggermesh/tree/main)
[![Go Report Card](https://goreportcard.com/badge/github.com/triggermesh/triggermesh)](https://goreportcard.com/report/github.com/triggermesh/triggermesh)
[![Slack](https://img.shields.io/badge/Slack-Join%20chat-4a154b?style=flat&logo=slack)](https://join.slack.com/t/triggermesh-community/shared_invite/zt-1kngevosm-MY7kqn9h6bT08hWh8PeltA)

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.

## Getting Started

* [Guides](https://docs.triggermesh.io/guides/creatingadls/)
* [Documentation](https://docs.triggermesh.io)

## Installation

To install TriggerMesh, follow the [installation instructions](https://docs.triggermesh.io/installation/).

### TL;DR

Register TriggerMesh APIs by deploying the Custom Resources Definitions:

```shell
kubectl apply -f https://github.com/triggermesh/triggermesh/releases/latest/download/triggermesh-crds.yaml
```

Deploy the platform:

```shell
kubectl apply -f https://github.com/triggermesh/triggermesh/releases/latest/download/triggermesh.yaml
```

### Namespaced installation

By 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:

```shell
kubectl apply -f https://github.com/triggermesh/triggermesh/releases/latest/download/triggermesh-crds.yaml
```

And then, using kubectl's "kustomization" feature, install customized manifests:

```shell
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.

## Contributing

Please refer to our [guidelines for contributors](CONTRIBUTING.md).

## Commercial Support

TriggerMesh Inc. offers commercial support for the TriggerMesh platform. Email us at to get more
details.

## License

This software is licensed under the [Apache License, Version 2.0][asl2].

Additionally, the End User License Agreement included in the [`EULA.pdf`](EULA.pdf) file applies to compiled
executables and container images released by TriggerMesh Inc.

[asl2]: https://www.apache.org/licenses/LICENSE-2.0