From 2f06f78bb197487b5ae42bc3f4d88bf72506ecab Mon Sep 17 00:00:00 2001 From: AlexejPenner Date: Tue, 17 Sep 2024 09:50:09 +0200 Subject: [PATCH 1/2] Fixed kubeflow docs --- docs/book/component-guide/orchestrators/kubeflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/book/component-guide/orchestrators/kubeflow.md b/docs/book/component-guide/orchestrators/kubeflow.md index 9ff19e45594..d53c68aa956 100644 --- a/docs/book/component-guide/orchestrators/kubeflow.md +++ b/docs/book/component-guide/orchestrators/kubeflow.md @@ -258,7 +258,7 @@ kubeflow_settings = KubeflowOrchestratorSettings( @pipeline( settings={ - "orchestrator": kubeflow_settings + "orchestrator.kubeflow": kubeflow_settings } ) From 680fc3e718561a14e0f3bc9c7496ba74a2984627 Mon Sep 17 00:00:00 2001 From: AlexejPenner Date: Tue, 17 Sep 2024 09:59:17 +0200 Subject: [PATCH 2/2] Fixed other small error in the docs --- docs/book/component-guide/orchestrators/kubeflow.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/book/component-guide/orchestrators/kubeflow.md b/docs/book/component-guide/orchestrators/kubeflow.md index d53c68aa956..2fa0b5140fa 100644 --- a/docs/book/component-guide/orchestrators/kubeflow.md +++ b/docs/book/component-guide/orchestrators/kubeflow.md @@ -177,7 +177,7 @@ We can then register the orchestrator and use it in our active stack. This can b Active global stack set to:'aws-kubeflow' ``` -2. if you don't have a Service Connector on hand and you don't want to [register one](../../how-to/auth-management/service-connectors-guide.md#register-service-connectors), the local Kubernetes `kubectl` client needs to be configured with a configuration context pointing to the remote cluster. The `kubernetes_context` stack component must also be configured with the value of that context: +2. if you don't have a Service Connector on hand and you don't want to [register one](../../how-to/auth-management/service-connectors-guide.md#register-service-connectors), the local Kubernetes `kubectl` client needs to be configured with a configuration context pointing to the remote cluster. The `kubernetes_context` must also be configured with the value of that context: ```shell zenml orchestrator register \ @@ -258,7 +258,7 @@ kubeflow_settings = KubeflowOrchestratorSettings( @pipeline( settings={ - "orchestrator.kubeflow": kubeflow_settings + "orchestrator": kubeflow_settings } )