From 61dedb1bbd706db784c190797e4a5cd791cb67e9 Mon Sep 17 00:00:00 2001 From: "Yuan (Bob) Gong" <4957653+Bobgy@users.noreply.github.com> Date: Wed, 18 Aug 2021 12:00:37 +0800 Subject: [PATCH] docs(gcp): ai platform pipelines use emissary tooltip update (#6331) * docs(gcp): ai platform pipelines use emissary tooltip update * update * address feedback --- manifests/gcp_marketplace/schema.yaml | 23 ++++++----------------- 1 file changed, 6 insertions(+), 17 deletions(-) diff --git a/manifests/gcp_marketplace/schema.yaml b/manifests/gcp_marketplace/schema.yaml index ab419ab10a5..fc9f39f794c 100644 --- a/manifests/gcp_marketplace/schema.yaml +++ b/manifests/gcp_marketplace/schema.yaml @@ -174,25 +174,14 @@ properties: title: Use emissary executor (Alpha) default: false description: |- - Kubeflow Pipelines default to use docker executor. Select this option to - use [the emissary executor (Alpha)](https://github.com/kubeflow/pipelines/issues/6249). + Warning, Kubeflow Pipelines does not work on Google Kubernetes Engine (GKE) 1.19+ by + default. You cluster node image must be configured to use docker as container runtime. - Refer to migrating to emissary executor documentation for migration instructions. + Using emissary executor removes the restriction on container runtime, but note some of + your pipelines may require manual migrations. - Emissary executor is more portable. On Google Kubernetes Engine (GKE) - clusters 1.19+, containerd is the default container runtime instead of - docker, so docker executor does not work properly. Emissary executor is not - coupled to a specific container runtime, so it works properly on any - Kubernetes clusters including GKE 1.19+ with containerd as runtime. - - If you want to keep using docker executor for GKE 1.19+, you need to configure - your node pools to use docker as container runtime by selecting "Container-Optimized OS with Docker (cos)" - (deprecated) as the node image. For more information, refer to - [GKE Node Images](https://cloud.google.com/kubernetes-engine/docs/concepts/node-images). - - Although emissary is in Alpha, Kubeflow Pipelines team is actively helping - to make it mature. Welcome any feedback if you have already tried emissary - executor: https://github.com/kubeflow/pipelines/issues/6249. + Refer to Argo Workflow Executors documentation for detailed configuration and migration instructions for both options: + https://www.kubeflow.org/docs/components/pipelines/installation/choose-executor/ managedstorage.enabled: type: boolean title: Use managed storage