Skip to content

Remove ingress-less term from tunnel-based #273

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 8, 2022
Merged

Remove ingress-less term from tunnel-based #273

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _docs/getting-started/architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions _docs/runtime/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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**

Expand Down
2 changes: 1 addition & 1 deletion _docs/runtime/monitor-manage-runtimes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
4 changes: 2 additions & 2 deletions _docs/whats-new/whats-new.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down