Remove ingress-less term from tunnel-based (#273)

Author: NimRegev

_docs/getting-started/architecture.md

@@ -82,7 +82,7 @@ In the hosted environment, the Codefresh Runtime is installed on a K8s cluster m
 %}
 
 #### Tunnel-based hybrid runtime architecture
-Tunnel-based hybrid runtimes use tunneling instead of ingress controllers to control communication between the Codefresh Runtime in the customer cluster and the Codefresh Platform. Tunnel-based, ingress-less, runtimes are optimal when the cluster with the Codefresh Runtime is not exposed to the internet. 
+Tunnel-based hybrid runtimes use tunneling instead of ingress controllers to control communication between the Codefresh Runtime in the customer cluster and the Codefresh Platform. Tunnel-based runtimes are optimal when the cluster with the Codefresh Runtime is not exposed to the internet. 
 
 {% include
    image.html

_docs/runtime/installation.md

@@ -133,7 +133,7 @@ The access mode for the runtime, which can be one of the following:
 
 * CLI wizard: Select the access mode from the list displayed.
 * Silent install:  
-  * For tunnel-based, see [Tunnel-based (ingress-less) runtime flags](#tunnel-based-ingress-less-runtime-flags)
+  * For tunnel-based, see [Tunnel-based runtime flags](#tunnel-based-runtime-flags)
   * For ingress-based, add the [Ingress controller flags](#ingress-controller-flags)
 
   >If you don't specify any flags, tunnel-based access is automatically selected.  
@@ -148,7 +148,7 @@ The Git repository per runtime account with shared configuration manifests.
 </br>
 {:/}
 
-#### Tunnel-based (ingress-less) runtime flags
+#### Tunnel-based runtime flags
 
 **IP allowlist**
 

_docs/runtime/monitor-manage-runtimes.md

@@ -33,7 +33,7 @@ Manage provisioned runtimes:
 * [Upgrade Codefresh CLI](#upgrade-codefresh-cli)
 * [Uninstall provisioned runtimes](#uninstall-provisioned-runtimes)
 * [Update Git tokens for runtimes](#update-git-tokens-for-runtimes)
-<!--* [Migrate ingress-less hybrid runtimes](#hybrid-migrate-ingress-less-runtimes) -->
+<!--* [Migrate access mode for hybrid runtimes](#hybrid-migrate-runtimes) -->
 
 > Unless specified otherwise, management options are common to both hybrid and hosted runtimes. If an option is valid only for hybrid runtimes, it is indicated as such. 
 

_docs/whats-new/whats-new.md

@@ -19,9 +19,9 @@ Built on Argo, the world’s most popular and fastest-growing open source softwa
 #### Tunnel-based hybrid runtimes
 Simplify installation without compromising on security with our tunnel-based installation option for hybrid runtimes.  
 
-Tunnel-based runtimes use tunneling for communication between the customer cluster and the Codefresh platform, with the customer cluster initiating the  tunneling request.   Simply add  the flag `--access-mode` with `tunnel` as the value and you have your tunnel-based, ingress-less runtime. 
+Tunnel-based runtimes use tunneling for communication between the customer cluster and the Codefresh platform, with the customer cluster initiating the  tunneling request.   Simply add  the flag `--access-mode` with `tunnel` as the value and you have your tunnel-based runtime without an ingress controller. 
 
-See [Tunnel-based runtime architecture]({{site.baseurl}}/docs/getting-started/architecture/#tunnel-based-hybrid-runtime-architecture) and [Tunnel-based runtime flags]({{site.baseurl}}/docs/runtime/installation/#tunnel-based-ingress-less-runtime-flags).
+See [Tunnel-based runtime architecture]({{site.baseurl}}/docs/getting-started/architecture/#tunnel-based-hybrid-runtime-architecture) and [Tunnel-based runtime flags]({{site.baseurl}}/docs/runtime/installation/#tunnel-based-runtime-flags).
 
 {::nomarkdown}
 <br>