diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 33116e32d..00ab9f0a9 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -8,7 +8,6 @@ *** xref:create-instance-task-flex.adoc[Add a Flex Gateway API Instance] *** xref:create-instance-task-mcp.adoc[Add a Flex Gateway MCP Server Instance] *** xref:create-instance-task-a2a.adoc[Add a Flex Gateway A2A Server 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] diff --git a/modules/ROOT/pages/_partials/api-configuration-tables.adoc b/modules/ROOT/pages/_partials/api-configuration-tables.adoc index 4052d1690..ad2a57a13 100644 --- a/modules/ROOT/pages/_partials/api-configuration-tables.adoc +++ b/modules/ROOT/pages/_partials/api-configuration-tables.adoc @@ -77,26 +77,6 @@ |=== //end::flex-upstream-a2a[] - -//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%"] |=== diff --git a/modules/ROOT/pages/_partials/task-add-api-instance.adoc b/modules/ROOT/pages/_partials/task-add-api-instance.adoc index c7a36ac1e..4ee7f905e 100644 --- a/modules/ROOT/pages/_partials/task-add-api-instance.adoc +++ b/modules/ROOT/pages/_partials/task-add-api-instance.adoc @@ -27,19 +27,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::server-intro2[] -The following diagram shows the server instance's upstream and downstream configurations. In this configuration, the downstream service is the service making requests that are completed by the upstream server. These terms represent the direction of dependency, not the direction of information. - -image:server-upstream-downstream-config.png[The server instance is deployed on a gateway between the upstream and downstream configuration] - -//end::server-intro2[] - //tag::intro2[] There are three options for adding an API instance: diff --git a/modules/ROOT/pages/add-api-instances.adoc b/modules/ROOT/pages/add-api-instances.adoc index 14d8a9f59..2e7848ad4 100644 --- a/modules/ROOT/pages/add-api-instances.adoc +++ b/modules/ROOT/pages/add-api-instances.adoc @@ -11,5 +11,3 @@ include::partial$task-add-api-instance.adoc[tags=flex-intro] include::partial$task-add-api-instance.adoc[tags=flex-mcp-intro] * xref:create-instance-task-a2a.adoc[] + include::partial$task-add-api-instance.adoc[tags=flex-a2a-intro] -* xref:create-instance-task-service-mesh.adoc[] + -include::partial$task-add-api-instance.adoc[tags=service-mesh-intro] diff --git a/modules/ROOT/pages/api-instance-landing-page.adoc b/modules/ROOT/pages/api-instance-landing-page.adoc index 0d57844f2..ff4bf7f0a 100644 --- a/modules/ROOT/pages/api-instance-landing-page.adoc +++ b/modules/ROOT/pages/api-instance-landing-page.adoc @@ -18,7 +18,6 @@ To manage API instances in API Manager: ** xref:create-instance-task-flex.adoc[] ** xref:create-instance-task-mcp.adoc[] ** xref:create-instance-task-a2a.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. diff --git a/modules/ROOT/pages/create-instance-task-service-mesh.adoc b/modules/ROOT/pages/create-instance-task-service-mesh.adoc deleted file mode 100644 index e3e0f1b04..000000000 --- a/modules/ROOT/pages/create-instance-task-service-mesh.adoc +++ /dev/null @@ -1,42 +0,0 @@ -= Adding a Service Mesh API Instance -ifndef::env-site,env-github[] -include::_attributes.adoc[] -endif::[] -:product: service-mesh -:page-notice-banner-message: This product is scheduled for End of Life. To integrate your micro services with Anypoint Platform, use Flex Gateway. For more information, see Integrating Flex Gateway with Istio Service Mesh - -include::partial$task-add-api-instance.adoc[tags=intro1;service-mesh-intro;intro2] - -[[add-api]] -== Add a New API - -. Navigate to *Anypoint Platform* > *API Manager*. -. In *API Administration*, click *Add API* and select *Add new API*. -. Select *Service Mesh*. -+ -NOTE: After adding the API on Anypoint Platform, you need to bind it to a service using the Anypoint Service Mesh client. See xref:service-mesh::configure-service-mesh.adoc#methods-for-configuring-anypoint-service-mesh[Methods for Configuring Anypoint Service Mesh] for more information. -. Click *Next*. -+ -include::partial$task-add-api-instance.adoc[tags=mid-steps;asset-type-options] - -. Configure the downstream configuration settings: -+ -include::partial$api-configuration-tables.adoc[tags=service-mesh-downstream] -. Click *Next*. -. Configure the upstream configuration settings: -+ -include::partial$api-configuration-tables.adoc[tags=service-mesh-upstream] -. Click *Next*. -+ -include::partial$task-add-api-instance.adoc[tags=last-steps] - - -//promote-api -include::partial$task-promote-api.adoc[] - -//import-api -include::partial$task-import-api.adoc[] - -== Notes - -* Although OpenAPI Specification (OAS) 3.0 is supported, the callback feature is not. To work around this issue, either handle the callback outside of the Mule runtime engine domain or use an OAS 3.0 specification that does not use callbacks. diff --git a/modules/ROOT/pages/edit-api-endpoint-task.adoc b/modules/ROOT/pages/edit-api-endpoint-task.adoc index dc2975263..08b09ca9d 100644 --- a/modules/ROOT/pages/edit-api-endpoint-task.adoc +++ b/modules/ROOT/pages/edit-api-endpoint-task.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: