Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Fix broken links#943

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.

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

Already on GitHub?Sign in to your account

Merged
NimRegev merged 7 commits intomasterfromfix-broken-links
Mar 11, 2024
Merged
Show file tree
Hide file tree
Changes fromall commits
Commits
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/integrations/codefresh-api.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -367,7 +367,7 @@ Encrypted variables cannot be read back by exporting the pipeline.

### Runtime environment

The `runtimeEnvironment` selects the cluster that will execute the pipeline (mostly useful for organizations using the [Codefresh Runner]({{site.baseurl}}/docs/installation/codefresh-runner/))
The `runtimeEnvironment` selects the cluster that will execute the pipeline (mostly useful for organizations using the [Codefresh Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/)).

{: .table .table-bordered .table-hover}
| Field name | Parent field | Type | Value |
Expand Down
4 changes: 3 additions & 1 deletion_docs/integrations/kubernetes.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -738,7 +738,9 @@ Codefresh also offers a simple solution for [templating]({{site.baseurl}}/docs/c

## Using a cluster for running CI/CD pipelines

Finally you can also use the [Codefresh Runner]({{site.baseurl}}/installation/docs/runner/install-codefresh-runner/) to run pipelines in your cluster.

Finally you can also use the [Codefresh Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner//) to run pipelines in your cluster.




Expand Down
2 changes: 1 addition & 1 deletion_docs/integrations/secret-storage.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -97,7 +97,7 @@ where:
## Secret store setup for Codefresh Runner installation


For [Codefresh Runner]({{site.baseurl}}/docs/installation/codefresh-runner/) installations, you can also store secrets in your own runtime.
For [Codefresh Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/) installations, you can also store secrets in your own runtime.

### Set up runtime secret store in Codefresh UI

Expand Down
2 changes: 1 addition & 1 deletion_docs/pipelines/pipeline-caching.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -200,7 +200,7 @@ This means that unlike other CI solutions where you have to manually describe wh
The main choice that you have is which files to place on the volume. For example, Node.js uses the folder `node_modules` for its dependencies which are placed under the project folder [which is automatically placed under the volume]({{site.baseurl}}/docs/pipelines/introduction-to-codefresh-pipelines/#cloning-the-source-code). So all contents of `node_modules` will be cached by default without any further action on your part.

>**NOTE**
If you are using [Codefresh on-premises]({{site.baseurl}}/docs/installation/codefresh-on-prem/), this kind of caching is not available for the built-in runtime.<br>You need to use the [Codefresh Runner]({{site.baseurl}}/docs/installation/codefresh-runner/) with your own runtime to activate volume caching.
If you are using [Codefresh on-premises]({{site.baseurl}}/docs/installation/installation-options/on-premises/), this kind of caching is not available for the built-in runtime.<br>You need to use the [Codefresh Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/) with your own runtime to activate volume caching.

The simplest way to see this caching mechanism in action is this pipeline:

Expand Down
2 changes: 1 addition & 1 deletion_docs/pipelines/pipelines.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -403,7 +403,7 @@ max-width="50%"
%}

**Configure runtime environment**<br>
As an account admin, if the account is not configured with a runtime environment, Codefresh displays the steps to [install the Runner]({{site.baseurl}}/docs/installation/codefresh-runner/).
As an account admin, if the account is not configured with a runtime environment, Codefresh displays the steps to [install the Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/).

{% include
image.html
Expand Down
2 changes: 1 addition & 1 deletion_docs/quick-start/gitops-quick-start/runtime.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -46,7 +46,7 @@ kubectl annotate --overwrite crds $(kubectl get crd | grep argoproj.io | awk '{p
### Tunnel-based Runtime
Hybrid GitOps Runtimes support tunnel-based, ingress-based, and service-mesh-based access modes.
For the quick start, we'll use the tunnel-based mode which is the default access mode that does not require an ingress controller.
For details on these access modes, review [GitOps Runtime architecture]({{site.baseurl}}/docs/installation/runtime-architecture/#gitops-runtime-architecture).
For details on these access modes, review [GitOps Runtime architecture]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/).

### GitHub as Git provider
Hybrid GitOps Runtimes require a Git Runtime token for authentication to the Git installation repository based on your Git provider, and a Git user token to authenticate Git-based actions for the Runtime.
Expand Down
2 changes: 1 addition & 1 deletion_posts/2022-10-15-october-gitops.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -15,7 +15,7 @@ We have changed the routing mechanism for hybrid runtimes. URL requests and webh

The change is effective from runtime version 0.0.543 and higher. If you already have runtimes installed, this change does not require any action from you, both to upgrade to the new runtime version or retain existing runtimes. Older runtimes continue to use the ingress controller for routing purposes.

See the description for Request Routing Service in [Hybrid runtime architecture]({{site.baseurl}}/docs/installation/runtime-architecture/#gitops-runtime-architecture).
See the description for Request Routing Service in [Hybrid runtime architecture]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/).

### More Git providers for runtimes

Expand Down
3 changes: 1 addition & 2 deletions_posts/2022-11-15-november-gitops.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -12,8 +12,7 @@ Simplify installation without compromising on security with our tunnel-based ins
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/installation/runtime-architecture/#gitops-runtime-architecture)
* [Tunnel-based runtime architecture]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/)
* [Runtime flags]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops/#runtime-flags)
* [Tunnel-based runtime flags]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops/#tunnel-based-runtime-flags)

Expand Down
[8]ページ先頭
©2009-2025 Movatter.jp