Skip to content

Commit

Permalink
Add instructions to enable controlplane wf execution
Browse files Browse the repository at this point in the history
Signed-off-by: davidmirror-ops <[email protected]>
  • Loading branch information
davidmirror-ops committed Oct 5, 2023
1 parent 83d8c35 commit e784efd
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions rsts/deployment/deployment/multicluster.rst
Original file line number Diff line number Diff line change
Expand Up @@ -375,7 +375,9 @@ label has to be 1.
10. Update the control plane Helm release:
.. note::
This step will disable ``flytepropeller`` in the control plane cluster, leaving no possibility of running workflows there.
This step will disable ``flytepropeller`` in the control plane cluster, leaving no possibility of running workflows there. If you require
the control plane to run workflows, edit the ``values-controlplane.yaml`` file and set ``flytepropeller.enabled`` to ``true``. Then, perform the ``helm upgrade`` operation and complete the steps in :ref:`this section <dataplane-deployment>` to configure it
as a dataplane cluster.
.. tabbed:: AWS
Expand Down Expand Up @@ -651,7 +653,7 @@ The process can be repeated for additional clusters.
.. prompt:: bash $
pyflyte run --remote --project team1 --domain production example.py training_workflow \  ✔ ╱ base 
pyflyte run --remote --project team1 --domain production example.py training_workflow \
--hyperparameters '{"C": 0.1}'
15. A successful execution should be visible on the UI, confirming it ran in the new cluster:
Expand Down

0 comments on commit e784efd

Please sign in to comment.