docs(gcp): ai platform pipelines use emissary tooltip update

[Bobgy]

Description of your changes:
Part of #6294

before the PR, it looked like the following on the UI, basically the format doesn't support markdown, so I have to reduce the number of links and what content to include here:

Checklist:

• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

[shuesc1]

"Docker executor does not work on Google Kubernetes Engine (GKE) 1.19+ by default, as docker container runtime is no longer the default container runtime; docker container runtime will be deprecated on GKE 1.20+."

[shuesc1]

".....refer to [1] for more details." -> "refer to Argo Workflow Executors[1] for more details."

[shuesc1]

"...use docker as a container runtime by selecting "Container-Optimized OS with Docker (cos)" (deprecated) as the node image[2]."

[kramachandran]

This feels way to long to be a tool tip -- can we shorten it? Just focus on two facts - you need Emissary if you want to GKE 1.19+; and that it causes a breaking change?

[zijianjoy]

How does the following description sound?

Warning: Use emissary executor for GKE 1.19+. Docker container runtime is no longer the default node image option since GKE 1.19.

[Bobgy]

Thank you for the review!
Let me try to resolve Karthik's comment first.

This feels way too long to be a tool tip -- can we shorten it? Just focus on two facts - you need Emissary if you want to GKE 1.19+; and that it causes a breaking change?

I think this is a great advice. For clarification, on GKE 1.19+, people can configure node image to use docker container runtime + docker executor too.

What do you think about rough ideas of the following?

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.

Using emissary executor removes the restriction on container runtime, but note some of
your pipelines may require manual migrations.

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/

[karkumar]

Thanks the updated text seems much clearer.

[Bobgy]

/approve

[google-oss-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bobgy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• manifests/gcp_marketplace/OWNERS [Bobgy]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment