Skip to content

Commit

Permalink
Update Readme to add the description of Maestro (#72)
Browse files Browse the repository at this point in the history
* Update Readme to add the description of Maestro

Signed-off-by: clyang82 <[email protected]>

* Address review comments

Signed-off-by: clyang82 <[email protected]>

---------

Signed-off-by: clyang82 <[email protected]>
  • Loading branch information
clyang82 authored Apr 2, 2024
1 parent fe88acd commit 1e08a6a
Show file tree
Hide file tree
Showing 3 changed files with 8 additions and 2 deletions.
10 changes: 8 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
Maestro
---
# Maestro
Maestro is a system to leverage [CloudEvents](https://cloudevents.io/) to transport Kubernetes resources to the target clusters, and then transport the resource status back. The resources are stored in a database and the status is updated in the database as well. The system is composed of two parts: the Maestro server and the Maestro agent.
- The Maestro server is responsible for storing the resources and their status. And sending the resources to the message broker in the CloudEvents format. The Maestro server provides Resful APIs and gRPC APIs to manage the resources.
- Maestro agent is responsible for receiving the resources and applying them to the target clusters. And reporting back the status of the resources.

## Architecture
Taking MQTT as an example:
![Maestro Architecture](./arch.png)

## Run for the first time

Expand Down
Binary file added arch.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed img.png
Binary file not shown.

0 comments on commit 1e08a6a

Please sign in to comment.