Remove service mesh

Author: glenn-rodgers-sf

modules/ROOT/nav.adoc

@@ -6,7 +6,6 @@
  ** xref:add-api-instances.adoc[Add API Instances]
  *** xref:create-instance-task-flex.adoc[Add a Flex Gateway API Instance]
  *** xref:create-instance-task-mule.adoc[Add a Mule Gateway API Instance]
- *** xref:create-instance-task-service-mesh.adoc[Add a Service Mesh API Instance]
  ** xref:find-api-id-task.adoc[Obtain an API Instance ID]
  ** xref:export-api-latest-task.adoc[Export an API Instance]
  ** xref:access-developer-portal-task.adoc[Access the Developer Portal]

modules/ROOT/pages/_partials/api-configuration-tables.adoc

@@ -22,25 +22,6 @@
 |===
 //end::flex-upstream[]
 
-//tag::service-mesh-downstream[]
-[%header%autowidth.spread,cols="15%,35%,15%,35%"]
-|===
-| Field Name | Description | Required | Notes
-| *Instance label* | Specifies a label for the API. | No | If you have multiple managed instances of the same API, add a label to differentiate each instance from the others.
-| *Advanced Options* |  |  |
-| *Consumer endpoint* | Specifies a proxy application's address for consumers to use for sending requests.| No |
-| *Client provider* | Specifies a client provider for the API. | Yes | Anypoint Platform acts as the client provider by default. To configure an external client provider, see xref:access-management::managing-api-clients.adoc[Client Providers]. 
-|===
-//end::service-mesh-downstream[]
-
-//tag::service-mesh-upstream[]
-[%header%autowidth.spread,cols="15%,35%,15%,35%"]
-|===
-| Field Name | Description | Required | Notes
-| *Upstream URL* | The URL to access for the proxy or the API. | No |  For example, you can use the URL of your API asset in Exchange. 
-|===
-//end::service-mesh-upstream[]
-
 //tag::mule-app-downstream[]
 [%header%autowidth.spread,cols="15%,35%,15%,35%"]
 |===

modules/ROOT/pages/_partials/task-add-api-instance.adoc

@@ -15,12 +15,6 @@ and secure your APIs.
 
 //end::mule-intro[]
 
-//tag::service-mesh-intro[]
-Use Anypoint Service Mesh to extend Anypoint Platform API Management capabilities to your
-Istio service mesh through the deployment of a Mule Adapter.
-
-//end::service-mesh-intro[]
-
 //tag::intro2[]
 
 There are three options for adding an API instance:

modules/ROOT/pages/add-api-instances.adoc

@@ -7,5 +7,3 @@ endif::[]
 include::partial$task-add-api-instance.adoc[tags=flex-intro]
 * xref:create-instance-task-mule.adoc[] +
 include::partial$task-add-api-instance.adoc[tags=mule-intro]
-* xref:create-instance-task-service-mesh.adoc[] +
-include::partial$task-add-api-instance.adoc[tags=service-mesh-intro]

modules/ROOT/pages/api-instance-landing-page.adoc

@@ -16,7 +16,6 @@ To manage API instances in API Manager:
 . Add an API instance for your relevant gateway:
 ** xref:create-instance-task-flex.adoc[]
 ** xref:create-instance-task-mule.adoc[] 
-** xref:create-instance-task-service-mesh.adoc[]
 . View an API instance's API Summary for information about the instance or to export it:
 ** xref:find-api-id-task.adoc[] - API Manager generates the apiId of new APIs managed by API Manager for use with Mule 4.
 ** xref:export-api-latest-task.adoc[] - After creating an API instance, you can export it. This exports the API instance endpoint configuration and Exchange asset relationship. You can then import it into another environment in the same business group to create a new API instance.

modules/ROOT/pages/create-instance-task-service-mesh.adoc

@@ -8,8 +8,7 @@ After you create an API instance in API Manager, you can edit the instance's con
 For more information about the API endpoint configuration settings, see:
 
 * xref:create-instance-task-flex.adoc[]
-* xref:create-instance-task-mule.adoc[] 
-* xref:create-instance-task-service-mesh.adoc[]
+* xref:create-instance-task-mule.adoc[]
 
 To edit an API instance's endpoint: