Skip to content

Commit

Permalink
Fix typos
Browse files Browse the repository at this point in the history
Signed-off-by: davidmirror-ops <[email protected]>
  • Loading branch information
davidmirror-ops committed Sep 29, 2023
1 parent 08692a7 commit be2abfd
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions rsts/deployment/deployment/multicluster.rst
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Multiple Kubernetes Cluster Deployment
.. note::

The multicluster deployment described in this section, assumes you have deployed
the ``flyte-core`` Helm chart, which runs the individual Flyte componentes separately.
the ``flyte-core`` Helm chart, which runs the individual Flyte components separately.
This is needed because in a multicluster setup, the execution engine is
deployed to multiple K8s clusters; it won't work with the ``flyte-binary``
Helm chart, since it deploys all Flyte services as one single binary.
Expand Down Expand Up @@ -502,7 +502,7 @@ Kubernetes cluster.
example.training_workflow \
--attrFile workflow-ecl.yaml

3. Execute a workflow indicationg project and domain:
3. Execute a workflow indicating project and domain:

.. prompt:: bash $

Expand Down Expand Up @@ -720,6 +720,6 @@ The process can be repeated for additional clusters.
pyflyte run --remote --project team1 --domain production example.py training_workflow \  ✔ ╱ base 
--hyperparameters '{"C": 0.1}'

18. A succesful execution should be visible on the UI, confirming it ran in the new cluster:
18. A successful execution should be visible on the UI, confirming it ran in the new cluster:

.. image:: https://raw.githubusercontent.com/flyteorg/static-resources/main/common/multicluster-execution.png

0 comments on commit be2abfd

Please sign in to comment.