Merge pull request #1234 from keithmattix/0.5.0-release-docs

Add experimental warning for resources that are experimental

site-src/blog/2021/introducing-v1alpha2.md

@@ -48,6 +48,13 @@ itself to the `prod-web-gw` Gateway.
 This is covered in more detail in [GEP 724](https://gateway-api.sigs.k8s.io/geps/gep-709/).
 
 ### Safe Cross Namespace References
+
+!!! info "Experimental Channel"
+
+    The `ReferenceGrant` resource described below is currently only included in the
+    "Experimental" channel of Gateway API. For more information on release
+    channels, refer to the [related documentation](https://gateway-api.sigs.k8s.io/concepts/versioning).
+
 It is quite challenging to cross namespace boundaries in a safe manner. With
 Gateway API, we had several key feature requests that required this capability.
 Most notably, forwarding traffic to backends in other namespaces and referring

site-src/concepts/api-overview.md

@@ -92,12 +92,26 @@ for either routing or modification, for example using HTTP Headers for routing,
 modifying them in-flight.
 
 #### TLSRoute
+
+!!! info "Experimental Channel"
+
+    The `TLSRoute` resource described below is currently only included in the
+    "Experimental" channel of Gateway API. For more information on release
+    channels, refer to the [related documentation](https://gateway-api.sigs.k8s.io/concepts/versioning).
+
 TLSRoute is for multiplexing TLS connections, discriminated via SNI. It's intended
 for where you want to use the SNI as the main routing method, and are not interested
 in properties of the higher-level protocols like HTTP.  The byte stream of the
 connection is proxied without any inspection to the backend.
 
 #### TCPRoute and UDPRoute
+
+!!! info "Experimental Channel"
+
+    The `TCPRoute` and `UDPRoute` resources described below are currently only included in the
+    "Experimental" channel of Gateway API. For more information on release
+    channels, refer to the [related documentation](https://gateway-api.sigs.k8s.io/concepts/versioning).
+
 TCPRoute (and UDPRoute) are intended for use for mapping one or more ports
 to a single backend. In this case, there is no discriminator you can
 use to choose different backends on the same port, so each TCPRoute really needs a

site-src/v1alpha2/api-types/referencegrant.md

@@ -1,5 +1,11 @@
 # ReferenceGrant
 
+!!! info "Experimental Channel"
+
+    The `ReferenceGrant` resource described below is currently only included in the
+    "Experimental" channel of Gateway API. For more information on release
+    channels, refer to the [related documentation](https://gateway-api.sigs.k8s.io/concepts/versioning).
+
 !!! note
     This resource was originally named "ReferencePolicy". It was renamed
     to "ReferenceGrant" to avoid any confusion with policy attachment.

site-src/v1alpha2/guides/tcp.md

@@ -1,3 +1,9 @@
+!!! info "Experimental Channel"
+
+    The `TCPRoute` resource described below is currently only included in the
+    "Experimental" channel of Gateway API. For more information on release
+    channels, refer to the [related documentation](https://gateway-api.sigs.k8s.io/concepts/versioning).
+
 Gateway API is designed to work with multiple protocols and [TCPRoute][tcproute]
 is one such route which allows for managing [TCP][tcp] traffic.
 

site-src/v1alpha2/guides/tls.md

@@ -4,6 +4,12 @@ Gateway API allow for a variety of ways to configure TLS. This document lays
 out various TLS settings and gives general guidelines on how to use them
 effectively.
 
+!!! info "Experimental Channel"
+
+    The `TLSRoute` resource described below is currently only included in the
+    "Experimental" channel of Gateway API. For more information on release
+    channels, refer to the [related documentation](https://gateway-api.sigs.k8s.io/concepts/versioning).
+
 ## Client/Server and TLS
 
 ![overview](/v1alpha2/images/tls-overview.svg)