diff --git a/docs/analysis/plugins.md b/docs/analysis/plugins.md
index 89f8f7a782..a7fd159a4a 100644
--- a/docs/analysis/plugins.md
+++ b/docs/analysis/plugins.md
@@ -1,6 +1,7 @@
 # Metric Plugins
 
-!!! important Available since v1.5 - Status: Alpha
+!!! important
+    Available since v1.5 - Status: Alpha
 
 Argo Rollouts supports getting analysis metrics via 3rd party plugin system. This allows users to extend the capabilities of Rollouts
 to support metric providers that are not natively supported. Rollout's uses a plugin library called
diff --git a/docs/features/traffic-management/google-cloud.md b/docs/features/traffic-management/google-cloud.md
new file mode 100644
index 0000000000..8f285ce9cf
--- /dev/null
+++ b/docs/features/traffic-management/google-cloud.md
@@ -0,0 +1,21 @@
+# Google Cloud 
+
+With the introduction of the Kubernetes Gateway API it is now possible to use Argo Rollouts with all compliant implementations that support it. The integration is available with the [Argo Rollouts Gateway API plugin](https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/) currently hosted in Argo Labs.
+
+Useful resources:
+
+* [The Gateway API specification](https://gateway-api.sigs.k8s.io/)
+* [Support of the Gateway API in Google Cloud](https://cloud.google.com/kubernetes-engine/docs/concepts/gateway-api)
+* [Argo Rollouts Plugin capabilities](../plugins/) 
+* [Plugin for the Gateway API](https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi)
+
+The process involves the following steps:
+
+1. Creating a Kubernetes cluster with support for the Gateway API in Google Cloud
+1. Creating a Load balancer that is managed by the Gateway API in Google Cloud
+1. Installing Argo Rollouts + gateway API plugin in the cluster
+1. Defining a Rollout that takes advantage of the plugin
+
+For a full application that includes all manifests see the [plugin example](https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/tree/main/examples/google-cloud).
+
+
diff --git a/docs/features/traffic-management/index.md b/docs/features/traffic-management/index.md
index 5048965414..6850b62fe9 100644
--- a/docs/features/traffic-management/index.md
+++ b/docs/features/traffic-management/index.md
@@ -21,6 +21,8 @@ Argo Rollouts enables traffic management by manipulating the Service Mesh resour
 - [AWS ALB Ingress Controller](alb.md)
 - [Ambassador Edge Stack](ambassador.md)
 - [Apache APISIX](apisix.md)
+- [Google Cloud](google-cloud.md)
+- [Gateway API](plugins.md)
 - [Istio](istio.md)
 - [Nginx Ingress Controller](nginx.md)
 - [Service Mesh Interface (SMI)](smi.md)
diff --git a/docs/features/traffic-management/plugins.md b/docs/features/traffic-management/plugins.md
index 3e43d5234e..26e1d6c1bf 100644
--- a/docs/features/traffic-management/plugins.md
+++ b/docs/features/traffic-management/plugins.md
@@ -1,6 +1,7 @@
 # Traffic Router Plugins
 
-!!! important Available since v1.5 - Status: Alpha
+!!! important
+    Available since v1.5 - Status: Alpha
 
 Argo Rollouts supports getting analysis metrics via 3rd party plugin system. This allows users to extend the capabilities of Rollouts
 to support metric providers that are not natively supported. Rollout's uses a plugin library called
diff --git a/mkdocs.yml b/mkdocs.yml
index c7cdabc426..6e2f77f388 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -49,6 +49,7 @@ nav:
   - Ambassador: features/traffic-management/ambassador.md
   - APISIX: features/traffic-management/apisix.md
   - AWS ALB: features/traffic-management/alb.md
+  - Google Cloud: features/traffic-management/google-cloud.md
   - Istio: features/traffic-management/istio.md
   - NGINX: features/traffic-management/nginx.md
   - Plugins: features/traffic-management/plugins.md