From f3055e2d8c6d1b0ebf25ce0478db9e920bdfd171 Mon Sep 17 00:00:00 2001 From: Ana <84312885+AnaLoznianu@users.noreply.github.com> Date: Wed, 25 Oct 2023 18:23:33 +0300 Subject: [PATCH] Update developers/compute-to-data/compute-workflow.md Co-authored-by: Alex Coseru --- developers/compute-to-data/compute-workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developers/compute-to-data/compute-workflow.md b/developers/compute-to-data/compute-workflow.md index eb0e8fda..90386334 100644 --- a/developers/compute-to-data/compute-workflow.md +++ b/developers/compute-to-data/compute-workflow.md @@ -24,7 +24,7 @@ The consumer selects a preferred environment from the provider's list and initia 7. As a new job begins, volumes are created on the Kubernetes cluster, a task handled by the operator engine. 8. The cluster creates and allocates volumes for the job using the job volumes 9. The volumes are created and allocated to the pod -10. After volume creation and allocation, the operator engine initiates the `run script` on the pod configuration. +10. After volume creation and allocation, the operator engine starts "pod-configuration" as a new pod in the cluster. ## Loading Assets and Algorithms 11. The pod configuration requires the data asset and algorithm, prompting a request to the provider for retrieval.