Adding release notes for API Gateway v0.2

website/content/docs/api-gateway/tech-specs.mdx

@@ -22,6 +22,7 @@ Your datacenter must meet the following requirements prior to configuring the Co
 - Consul 1.11.2+
 - HashiCorp Consul Helm chart 0.43.0+
 - Consul Service Mesh must be deployed on the Kubernetes cluster that API Gateway is deployed on.
+- Envoy:  Envoy proxy support is determined by the Consul version deployed. Refer to [Envoy Integration](/docs/connect/proxies/envoy) for details.
 
 ### TCP Port Requirements
 

website/content/docs/release-notes/consul-api-gateway/v0_1_x.mdx

@@ -27,13 +27,14 @@ gateway functionality. It provides additional capabilities that ingress gateway
    internal CA.
 
 ## Release Highlights
+
 This release includes the following features and capabilities:
 
 1. Can be deployed in the following run time environments:
-  - Self-managed Kubernetes
-  - AWS EKS
-  - Google GKE
-  - Azure AKS.
+   - Self-managed Kubernetes
+   - AWS EKS
+   - Google GKE
+   - Azure AKS.
 1. Install via the  HashiCorp Consul Helm chart.
 1. Works with self-managed Consul servers and HCP Consul servers
 1. Configure via Kubernetes Gateway API - v1alpha2
@@ -48,7 +49,7 @@ This release includes the following features and capabilities:
    - HTTP Header
    - HTTP Method
    - HTTP Query parameters
-1  HTTP header manipulation:
+1. HTTP header manipulation:
    - Set header value
    - Add header and/or value
    - Remove header and/or value

website/content/docs/release-notes/consul-api-gateway/v0_2_x.mdx

@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 0.2.x
+description: >-
+  Consul API Gateway release notes for version 0.2.x
+---
+
+# Consul API Gateway 0.2.0
+
+## Release Highlights
+
+- **Cross Namespace Reference Policies:**  Reference Policies are security
+  mechanism in the Kubernetes Gateway API that allows users to better control
+  how traffic is routed between Kubernetes namespaces. With the previous
+  releases of Consul API Gateway, users could route requests from the API
+  Gateway across various namespaces without providing any sort of explicit
+  permissions. While this meant that any service connected to the service mesh
+  was reachable, it didn’t allow users to set the more granular restrictions or
+  permissions that they may expect.
+
+    This version of API Gateway implements Cross Namespace Reference Policies
+    and requires them when routes are in a different namespace than the services
+    (as specified by the `backendRef`) they are routing traffic to.
+
+## What's Changed
+
+- First change
+
+- Second change
+
+- Third change
+
+## Supported Software
+
+- Consul 1.11.2+
+- HashiCorp Consul Helm chart 0.43.0+
+- Kubernetes 1.21+
+- Kubectl 1.21+
+- Envoy proxy support is determined by the Consul version deployed. Refer to
+  [Envoy Integration](/docs/connect/proxies/envoy) for details.
+
+## Kubernetes Gateway API Specification
+
+Supported version of the Gateway API spec: `v1alpha2`(v0.4.1)
+
+
+## Upgrading
+
+~>**Note**: If your current deployment has routes and and services that cross namespaces, those routes will not be applied to their gateways until cross namespace reference policies are created for them.
+
+For detailed information on upgrading, including how to create the required refeence policies, please refer to the [upgrade details page](/docs/api-gateway/upgrade-specific-versions)
+
+## Change logs
+
+The changelogs for this major release version and any maintenance versions are listed below.
+
+-> **Note**: These links will take you to the changelogs on the GitHub website.
+
+- [0.2.0](https://github.com/hashicorp/consul-api-gateway/releases/tag/v0.2.0)

website/data/docs-nav-data.json

@@ -1222,6 +1222,10 @@
           {
             "title": "v0.1.x",
             "path": "release-notes/consul-api-gateway/v0_1_x"
+          },
+          {
+            "title": "v0.2.x",
+            "path": "release-notes/consul-api-gateway/v0_2_x"
           }
         ]
       },