-
Notifications
You must be signed in to change notification settings - Fork 129
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Revital Sur <[email protected]>
- Loading branch information
Showing
1 changed file
with
5 additions
and
5 deletions.
There are no files selected for viewing
10 changes: 5 additions & 5 deletions
10
kfp/add_new_kfp_workflow.md → transforms/add_new_kfp_workflow.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,13 @@ | ||
# Adding new KFP workflows | ||
|
||
This README outlines the steps to add a new KFP workflow for a new transform: | ||
This README outlines the steps to add a new KFP workflow for a new transform under [transforms](./transforms/) directory. | ||
|
||
1) Create the workflow. [pipeline generator](./pipeline_generator/single-pipeline/) can be used for that. | ||
1) Create the workflow. [pipeline generator](../kfp/pipeline_generator/single-pipeline/) can be used for that. | ||
|
||
2) Create a new `kfp_ray` directory in the transform directory, similar to [this directory](../transforms/universal/noop/kfp_ray/). Inside this directory, include the following: | ||
2) Create a new `kfp_ray` directory in the transform directory, similar to [this directory](universal/noop/kfp_ray/). Inside this directory, include the following: | ||
- The workflow file created in the previous step. | ||
- `pipeline_definitions.yaml`, if the workflow was generated using the [pipeline generator](./pipeline_generator/single-pipeline/). | ||
- `Makefile` file similar to [this Makefile example](../transforms/universal/noop/kfp_ray/Makefile). | ||
- `pipeline_definitions.yaml`, if the workflow was generated using the [pipeline generator](../kfp//pipeline_generator/single-pipeline/). | ||
- `Makefile` file similar to [this Makefile example](./universal/noop/kfp_ray/Makefile). | ||
|
||
3) Add the path to the transform input directory in the [populate_minio script](../scripts/k8s-setup/populate_minio.sh). This path is used when testing the workflow. | ||
4) Create a GitHub Action for the kfp workflow using the `make` command in the [.github/workflows/](../.github/workflows/README.md) directory. |