From 026451249ff10bcf57435aa1b450b3ad540c07c1 Mon Sep 17 00:00:00 2001 From: Mathew Wicks <5735406+thesuperzapper@users.noreply.github.com> Date: Mon, 19 Aug 2024 12:46:48 -0700 Subject: [PATCH] Fix checklinks errors Signed-off-by: Mathew Wicks <5735406+thesuperzapper@users.noreply.github.com> --- .../en/docs/components/katib/user-guides/katib-config.md | 2 +- .../pipelines/legacy-v1/tutorials/api-pipelines.md | 2 +- .../components/pipelines/operator-guides/multi-user.md | 8 ++++---- .../pipelines/user-guides/core-functions/connect-api.md | 2 +- .../pipelines/user-guides/data-handling/artifacts.md | 2 +- .../en/docs/components/pipelines/user-guides/migration.md | 2 +- 6 files changed, 9 insertions(+), 9 deletions(-) diff --git a/content/en/docs/components/katib/user-guides/katib-config.md b/content/en/docs/components/katib/user-guides/katib-config.md index cbe9fd723f..c33996ea21 100644 --- a/content/en/docs/components/katib/user-guides/katib-config.md +++ b/content/en/docs/components/katib/user-guides/katib-config.md @@ -8,7 +8,7 @@ This guide describes [the Katib Config](https://github.com/kubeflow/katib/blob/19268062f1b187dde48114628e527a2a35b01d64/manifests/v1beta1/installs/katib-standalone/katib-config.yaml) — the main configuration file for every Katib component. We use Kubernetes [ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) to -fetch that config into [the Katib control plane components](/docs/components/katib/installation/#installing-control-plane). +fetch that config into [the Katib control plane components](/docs/components/katib/reference/architecture/#katib-control-plane-components). The ConfigMap must be deployed in the [`KATIB_CORE_NAMESPACE`](/docs/components/katib/user-guides/env-variables/#katib-controller) diff --git a/content/en/docs/components/pipelines/legacy-v1/tutorials/api-pipelines.md b/content/en/docs/components/pipelines/legacy-v1/tutorials/api-pipelines.md index 0758dc3bd9..5122e33b8e 100644 --- a/content/en/docs/components/pipelines/legacy-v1/tutorials/api-pipelines.md +++ b/content/en/docs/components/pipelines/legacy-v1/tutorials/api-pipelines.md @@ -39,7 +39,7 @@ wget -O ${PIPELINE_FILE} ${PIPELINE_URL} dsl-compile --py ${PIPELINE_FILE} --output ${PIPELINE_NAME}.tar.gz ``` -After running the commands above, you should get two files in your current directory: `sequential.py` and `sequential.tar.gz`. Run the following command to deploy the generated `.tar.gz` file as you would do using the [Kubeflow Pipelines UI](/docs/components/pipelines/user-guides/core-functions/run-a-pipeline/#1-run-from-the-kfp-dashboard), but this time using the REST API. +After running the commands above, you should get two files in your current directory: `sequential.py` and `sequential.tar.gz`. Run the following command to deploy the generated `.tar.gz` file as you would do using the [Kubeflow Pipelines UI](/docs/components/pipelines/user-guides/core-functions/run-a-pipeline/#run-pipeline---kfp-dashboard), but this time using the REST API. ``` SVC=localhost:8888 diff --git a/content/en/docs/components/pipelines/operator-guides/multi-user.md b/content/en/docs/components/pipelines/operator-guides/multi-user.md index a1774416d5..3f1d44fbcd 100644 --- a/content/en/docs/components/pipelines/operator-guides/multi-user.md +++ b/content/en/docs/components/pipelines/operator-guides/multi-user.md @@ -42,10 +42,10 @@ Pipeline definitions are not isolated right now, and are shared across all names How to connect Pipelines SDK to Kubeflow Pipelines will depend on __what kind__ of Kubeflow deployment you have, and __from where you are running your code__. -* [Full Kubeflow (from inside cluster)](/docs/components/pipelines/user-guides/core-functions/connect-api/#full-kubeflow-subfrom-inside-clustersub) -* [Full Kubeflow (from outside cluster)](/docs/components/pipelines/user-guides/core-functions/connect-api/#full-kubeflow-subfrom-outside-clustersub) -* [Standalone Kubeflow Pipelines (from inside cluster)](/docs/components/pipelines/user-guides/core-functions/connect-api/#standalone-kubeflow-pipelines-subfrom-inside-clustersub) -* [Standalone Kubeflow Pipelines (from outside cluster)](/docs/components/pipelines/user-guides/core-functions/connect-api/#standalone-kubeflow-pipelines-subfrom-outside-clustersub) +* [Full Kubeflow (from inside cluster)](/docs/components/pipelines/user-guides/core-functions/connect-api/#kubeflow-platform---inside-the-cluster) +* [Full Kubeflow (from outside cluster)](/docs/components/pipelines/user-guides/core-functions/connect-api/#kubeflow-platform---outside-the-cluster) +* [Standalone Kubeflow Pipelines (from inside cluster)](/docs/components/pipelines/user-guides/core-functions/connect-api/#standalone-kfp---inside-the-cluster) +* [Standalone Kubeflow Pipelines (from outside cluster)](/docs/components/pipelines/user-guides/core-functions/connect-api/#standalone-kfp---outside-the-cluster) The following Python code will create an experiment (and associated run) from a Pod inside a full Kubeflow cluster. diff --git a/content/en/docs/components/pipelines/user-guides/core-functions/connect-api.md b/content/en/docs/components/pipelines/user-guides/core-functions/connect-api.md index bb13ecbae3..31f1cff279 100644 --- a/content/en/docs/components/pipelines/user-guides/core-functions/connect-api.md +++ b/content/en/docs/components/pipelines/user-guides/core-functions/connect-api.md @@ -245,7 +245,7 @@ class KFPClientManager: # no cookies are needed return "" - # if we are at `.../auth` path, we need to select an auth type + # if we are at `../auth` path, we need to select an auth type url_obj = urlsplit(resp.url) if re.search(r"/auth$", url_obj.path): url_obj = url_obj._replace( diff --git a/content/en/docs/components/pipelines/user-guides/data-handling/artifacts.md b/content/en/docs/components/pipelines/user-guides/data-handling/artifacts.md index 3a32ca3f1d..7f040ebd30 100644 --- a/content/en/docs/components/pipelines/user-guides/data-handling/artifacts.md +++ b/content/en/docs/components/pipelines/user-guides/data-handling/artifacts.md @@ -245,7 +245,7 @@ On the [KFP open source][oss-be] UI, `ClassificationMetrics`, `SlicedClassificat [python-components]: /docs/components/pipelines/user-guides/components/lightweight-python-components [dsl-parallelfor]: https://kubeflow-pipelines.readthedocs.io/en/latest/source/dsl.html#kfp.dsl.ParallelFor [dsl-collected]: https://kubeflow-pipelines.readthedocs.io/en/latest/source/dsl.html#kfp.dsl.Collected -[parallel-looping]: /docs/components/pipelines/user-guides/core-functions/control-flow/#parallel-looping-dslparallelfor +[parallel-looping]: /docs/components/pipelines/user-guides/core-functions/control-flow/#dslparallelfor [traditional-artifact-syntax]: /docs/components/pipelines/user-guides/data-handling/artifacts/#traditional-artifact-syntax [multiple-outputs]: /docs/components/pipelines/user-guides/data-handling/parameters/#multiple-output-parameters [pythonic-artifact-syntax]: /docs/components/pipelines/user-guides/data-handling/artifacts/#new-pythonic-artifact-syntax \ No newline at end of file diff --git a/content/en/docs/components/pipelines/user-guides/migration.md b/content/en/docs/components/pipelines/user-guides/migration.md index f8502c647a..b86575d382 100644 --- a/content/en/docs/components/pipelines/user-guides/migration.md +++ b/content/en/docs/components/pipelines/user-guides/migration.md @@ -694,7 +694,7 @@ If you believe we missed a breaking change or an important migration step, pleas [new-issue]: https://github.com/kubeflow/pipelines/issues/new [oss-be-v1]: /docs/components/pipelines/legacy-v1/ [oss-be-v2]: /docs/components/pipelines/operator-guides/installation/ -[parallelfor-control-flow]: /docs/components/pipelines/user-guides/core-functions/control-flow/#parallel-looping-dslparallelfor +[parallelfor-control-flow]: /docs/components/pipelines/user-guides/core-functions/control-flow/#dslparallelfor [parameters]: /docs/components/pipelines/user-guides/data-handling/parameters [pipelines-repo]: https://github.com/kubeflow/pipelines [semver-minor-version]: https://semver.org/#:~:text=MINOR%20version%20when%20you%20add%20functionality%20in%20a%20backwards%20compatible%20manner