docs: update docs with some changes for v12 (#1097)

In V12, we are moving some parameters around to support the new naming
conventions. Also update docs with gateway/istio support.

Closes INF-1019

---------

Co-authored-by: Copilot <[email protected]>
Co-authored-by: Kathryn May <[email protected]>

Author: 3 people

src/langsmith/deploy-self-hosted-full-platform.mdx

@@ -36,8 +36,8 @@ This guide builds on top of the [Kubernetes installation guide](/langsmith/kuber
   helm install keda kedacore/keda --namespace keda --create-namespace
 ```
 6. Ingress Configuration
-    1. You must set up an ingress for your LangSmith instance. All agents will be deployed as Kubernetes services behind this ingress. Use this guide to [set up an ingress](/langsmith/self-host-ingress) for your instance.
-7. You have slack space in your cluster for multiple deployments. `Cluster-Autoscaler` is recommended to automatically provision new nodes.
+    1. You must set up an ingress, gateway, or use Istio for your LangSmith instance. All agents will be deployed as Kubernetes services behind this ingress. Use this guide to [set up an ingress](/langsmith/self-host-ingress) for your instance.
+7. You must have slack space in your cluster for multiple deployments. `Cluster-Autoscaler` is recommended to automatically provision new nodes.
 8. A valid Dynamic PV provisioner or PVs available on your cluster. You can verify this by running:
 ```bash
   kubectl get storageclass
@@ -60,9 +60,12 @@ This guide builds on top of the [Kubernetes installation guide](/langsmith/kuber
     repository: "docker.io/langchain/langgraph-operator"
     pullPolicy: IfNotPresent
 ```
-3. In your config file for langsmith (usually `langsmith_config.yaml`), enable the `langgraphPlatform` option. Note that you must also have a valid ingress setup:
+3. In your config file for langsmith (usually `langsmith_config.yaml`), enable the `deployment` option. Note that you must also have a valid ingress setup:
 ```bash
   config:
+    deployment:
+      enabled: true
+    # As of v0.12.0, this section is deprecated. Use config.deployment for any version after v0.12.0.
     langgraphPlatform:
       enabled: true
       langgraphPlatformLicenseKey: "YOUR_LANGGRAPH_PLATFORM_LICENSE_KEY"

src/langsmith/self-host-ingress.mdx

@@ -3,20 +3,23 @@ title: Create an Ingress for installations (Kubernetes)
 sidebarTitle: Create an Ingress for installations (Kubernetes)
 ---
 
-By default, LangSmith will provision a LoadBalancer service for the `langsmith-frontend`. Depending on your cloud provider, this may result in a public IP address being assigned to the service. If you would like to use a custom domain or have more control over the routing of traffic to your LangSmith installation, you can configure an Ingress.
+By default, LangSmith will provision a LoadBalancer service for the `langsmith-frontend`. Depending on your cloud provider, this may result in a public IP address being assigned to the service. If you would like to use a custom domain or have more control over the routing of traffic to your LangSmith installation, you can configure an Ingress, Gateway API, or Istio Gateway.
 
 ## Requirements
 
 * An existing Kubernetes cluster
-* An existing Ingress Controller installed in your Kubernetes cluster
+* One of the following installed in your Kubernetes cluster:
+  * An Ingress Controller (for standard Ingress)
+  * Gateway API CRDs and a Gateway resource (for Gateway API)
+  * Istio (for Istio Gateway)
 
 ## Parameters
 
 You may need to provide certain parameters to your LangSmith installation to configure the Ingress. Additionally, we will want to convert the `langsmith-frontend` service to a ClusterIP service.
 
 * *Hostname (optional)*: The hostname that you would like to use for your LangSmith installation. E.g `"langsmith.example.com"`. If you leave this empty, the ingress will serve all traffic to the LangSmith installation.
 
-* *Subdomain (optional)*: If you would like to serve LangSmith under a URL path, you can specify it here. For example, adding `"langsmith"` will serve the application at `"example.hostname.com/langsmith"`. This will apply to UI paths as well as API endpoints.
+* *BasePath (optional)*: If you would like to serve LangSmith under a URL basePath, you can specify it here. For example, adding `"langsmith"` will serve the application at `"example.hostname.com/langsmith"`. This will apply to UI paths as well as API endpoints.
 
 * *IngressClassName (optional)*: The name of the Ingress class that you would like to use. If not set, the default Ingress class will be used.
 
@@ -44,13 +47,20 @@ You may need to provide certain parameters to your LangSmith installation to con
 
 ## Configuration
 
+You can configure your LangSmith instance to use one of three routing options: standard Ingress, Gateway API, or Istio Gateway. Choose the option that best fits your infrastructure.
+
+### Option 1: Standard Ingress
+
 With these parameters in hand, you can configure your LangSmith instance to use an Ingress. You can do this by modifying the `config.yaml` file for your LangSmith Helm Chart installation.
 
 ```yaml
+config:
+  hostname: "" # Main domain for LangSmith
+  basePath: "" # If you want to serve langsmith under a URL base path (e.g., /langsmith)
 ingress:
   enabled: true
-  hostname: "" # Main domain for LangSmith
-  subdomain: "" # If you want to serve langsmith on a subdomain
+  hostname: "" # Deprecated: Use config.hostname instead after v0.12.0
+  subdomain: "" # Deprecated: Use config.hostname instead after v0.12.0
   ingressClassName: "" # If not set, the default ingress class will be used
   annotations: {} # Add annotations here if needed
   labels: {} # Add labels here if needed
@@ -76,3 +86,85 @@ langsmith-ingress            nginx   <host>   35.227.243.203   80, 443   95d
 <Warning>
 If you do not have automated DNS setup, you will need to add the IP address to your DNS provider manually.
 </Warning>
+
+### Option 2: Gateway API
+
+<Note>
+Gateway API support is available as of LangSmith v0.12.0
+</Note>
+
+If your cluster uses the [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/), you can configure LangSmith to provision HTTPRoute resources. This will create an HTTPRoute for LangSmith and an HTTPRoute for each [agent deployment](/langsmith/deployments).
+
+#### Parameters
+
+* *name (required)*: The name of the Gateway resource to reference
+* *namespace (required)*: The namespace where the Gateway resource is located
+* *hostname (optional)*: The hostname that you would like to use for your LangSmith installation. E.g `"langsmith.example.com"`
+* *basePath (optional)*: If you would like to serve LangSmith under a base path, you can specify it here. E.g "example.com/langsmith"
+* *sectionName (optional)*: The name of a specific listener section in the Gateway to use
+* *annotations (optional)*: Additional annotations to add to the HTTPRoute resources
+* *labels (optional)*: Additional labels to add to the HTTPRoute resources
+
+#### Configuration
+
+```yaml
+config:
+  hostname: "" # Main domain for LangSmith
+  basePath: "" # If you want to serve langsmith under a base path. E.g "example.com/langsmith"
+gateway:
+  enabled: true
+  name: "my-gateway" # Name of your Gateway resource
+  namespace: "gateway-system" # Namespace of your Gateway resource
+  sectionName: "" # Optional: specific listener section name
+  annotations: {} # Add annotations here if needed
+  labels: {} # Add labels here if needed
+frontend:
+  service:
+    type: ClusterIP
+```
+
+Once configured, you can check the status of your HTTPRoutes:
+
+```bash
+kubectl get httproute
+```
+
+### Option 3: Istio Gateway
+
+<Note>
+Istio Gateway support is available as of LangSmith v0.12.0
+</Note>
+
+If your cluster uses [Istio](https://istio.io/), you can configure LangSmith to provision VirtualService resources. This will create a VirtualService for LangSmith and a VirtualService for each [agent deployment](/langsmith/deployments).
+
+#### Parameters
+
+* *name (optional)*: The name of the Istio Gateway resource to reference. Defaults to `"istio-gateway"`
+* *namespace (optional)*: The namespace where the Istio Gateway resource is located. Defaults to `"istio-system"`
+* *hostname (optional)*: The hostname that you would like to use for your LangSmith installation. E.g `"langsmith.example.com"`
+* *basePath (optional)*: If you would like to serve LangSmith under a base path, you can specify it here. E.g "example.com/langsmith"
+* *annotations (optional)*: Additional annotations to add to the VirtualService resources
+* *labels (optional)*: Additional labels to add to the VirtualService resources
+
+#### Configuration
+
+```yaml
+config:
+  hostname: "" # Main domain for LangSmith
+  basePath: "" # If you want to serve langsmith on a separate basePath. E.g "example.com/langsmith"
+istioGateway:
+  enabled: true
+  name: "istio-gateway" # Name of your Istio Gateway resource
+  namespace: "istio-system" # Namespace of your Istio Gateway resource
+  annotations: {} # Add annotations here if needed
+  labels: {} # Add labels here if needed
+frontend:
+  service:
+    type: ClusterIP
+```
+
+Once configured, you can check the status of your VirtualServices:
+
+```bash
+kubectl get virtualservice
+```