Merge pull request #2862 from replicatedhq/AmberAlston-patch-1

Update testing-ingress.md

Author: AmberAlston

docs/vendor/testing-ingress.md

@@ -29,22 +29,18 @@ Ingress is also not perfectly portable; each ingress controller might require di
 Supported ingress controllers vary based on the distribution.
 Compatibility matrix supports ingress controllers that are running as a `NodePort` service.
 
-### Compatibility Matrix Tunnels (Beta)
+### Compatibility Matrix Tunnels
 All VM-based Compatibility Matrix clusters support tunneling traffic into a `NodePort` service. 
 When this option is used, Replicated is responsible for creating the DNS record and TLS certs.
-Replicated will route traffic from `:443` and/or `:80` into the `NodePort` service you defined. For more information about using tunnels, see [Managing Compatibility Matrix Tunnels (Beta)](#manage-nodes) below.
+Replicated will route traffic from `:443` and/or `:80` into the `NodePort` service you defined. For more information about using tunnels, see [Managing Compatibility Matrix Tunnels](#manage-nodes) below.
 
 The following diagram shows how the traffic is routed into the service using Compatibility Matrix tunnels:
 
 <img src="/images/compatibility-matrix-ingress.png" alt="Compatibility Matrix ingress"></img>
 
 [View a larger version of this image](/images/compatibility-matrix-ingress.png)
 
-## Managing Compatibility Matrix Tunnels (Beta) {#manage-nodes}
-
-:::note
-Compatibity matrix tunnels are a beta feature.
-:::
+## Managing Compatibility Matrix Tunnels {#manage-nodes}
 
 Tunnels are viewed, created, and removed using the Compatibility Matrix UI within Vendor Portal, the Replicated CLI, GitHub Actions, or directly with the Vendor API v3. There is no limit to the number of tunnels you can create for a cluster and multiple tunnels can connect to a single service, if desired.