You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
A Runtime in Codefresh is a GitOps installation in your Codefresh account, in either a Hosted or Hybrid installation environment. Hosted Runtimes are installed on a Codefresh cluster and managed by Codefresh. Hybrid Runtimes are installed on customer clusters, and managed by the customers.
Copy file name to clipboardExpand all lines: _docs/getting-started/gitops-codefresh.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ Codefresh offers two models for GitOps deployments:
51
51
* Hybrid GitOps, which is a customer-managed version of Argo CD. The Hybrid GitOps runtime is hosted on the customer cluster and managed by the customer.
52
52
The Hybrid GitOps offering retains runtimes within the customer infrastructure to comply your security rewhile giving you the power of Argo CD with Codefresh’s CI and CD tools, to help achieve continuous integration and continuous delivery goals.
Copy file name to clipboardExpand all lines: _docs/installation/runner/install-codefresh-runner.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -294,7 +294,7 @@ runtimeScheduler:
294
294
|`envVars`| object| Override or add environment variables passed into the dind pod. See[IN-DIND cleaner](https://github.com/codefresh-io/dind/tree/master/cleaner){:target="\_blank"}|
295
295
|`userVolumeMounts` with`userVolumes`| object| Add volume mounts to the pipeline.<br>See[Custom Volume Mounts](https://artifacthub.io/packages/helm/codefresh-runner/cf-runtime#custom-volume-mounts){:target="\_blank"}.|
296
296
|`cluster`| object| k8s related information (`namespace`,`serviceAccount`,`nodeSelector`)|
297
-
`defaultDindResources` | object | Override`requests` and`limits` for dind pod (defaults are`cpu: 400m` and`memory:800Mi`). For memory, use`Mi` (mebibytes); for CPU, use`m` (millicpu).<br>See also[How to: Update Runtime Environment memory and CPU settings]({{site.baseurl}}/docs/kb/articles/update-runtime-mem-cpu/). |
297
+
`defaultDindResources` | object | Override`requests` and`limits` for dind pod (defaults are`cpu: 400m` and`memory:800Mi`). For memory, use`Mi` (mebibytes); for CPU, use`m` (millicpu).<!---<br>See also [How to: Update Runtime Environment memory and CPU settings]({{site.baseurl}}/docs/kb/articles/update-runtime-mem-cpu/).--> |
298
298
|`tolerations`| array| Add tolerations to dind pod|
299
299
|`annotations`| object| Add custom annotations to dind pod (empty by default`{}`)|
300
300
|`labels`| object| Add custom labels to dind pod (empty by default`{}`)|
Configure the Codefresh Runner to use local SSDs for your pipeline volumes:
659
659
660
-
[How-to: Configuring an existing Runtime Environment with Local SSDs (GKE only)]({{site.baseurl}}/docs/kb/articles/config-re-gke-ssd){:target="\_blank"}
660
+
<!---[How-to: Configuring an existing Runtime Environment with Local SSDs (GKE only)]({{site.baseurl}}/docs/kb/articles/config-re-gke-ssd){:target="\_blank"} -->
Copy file name to clipboardExpand all lines: _docs/integrations/jira.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Set up a Jira integration for pipelines, and then reference the integration in y
13
13
14
14
Optionally, a[GitOps-based Jira integration](#gitops-based-jira-integration-for-image-enrichment) allows you to enrich images with Jira information through a different Marketplace step.
15
15
16
-
For information on Jira integration for notifications, see[Jira notification integrations for pipelines]({{site.baseurl}}/docs/integrations/jira-integration/).
16
+
For information on Jira integration for notifications, see[Jira notification integrations for pipelines]({{site.baseurl}}/docs/integrations/notifications/jira-integration/).