Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
> Orchestrates a compute job

![Travis (.com) branch](https://img.shields.io/travis/com/oceanprotocol/operator-engine/develop)
![GitHub contributors](https://img.shields.io/github/contributors/oceanprotocol/operator-engine)
[![GitHub contributors](https://img.shields.io/github/contributors/oceanprotocol/operator-engine)](https://github.com/oceanprotocol/operator-engine/graphs/contributors)


Table of Contents
Expand All @@ -30,7 +30,7 @@ Table of Contents
## About

The Operator Engine is a backend agent implementing part of the Ocean Protocol
[Compute to the Data OEP-12](https://github.com/oceanprotocol/OEPs/tree/master/12#infrastructure-orchestration),
[Compute to the Data OEP-12](https://github.com/oceanprotocol-archive/OEPs/tree/master/12),
in charge of orchestrate the compute infrastructure using Kubernetes as backend.
Typically the Operator Engine retrieve the Workflows created by the [Operator Service](https://github.com/oceanprotocol/operator-service),
in Kubernetes and manage the infrastructure necessary to complete the execution of the compute workflows.
Expand Down