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
Copy file name to clipboardExpand all lines: _docs/ci-cd-guides/gitops-deployments.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
@@ -8,7 +8,7 @@ toc: true
8
8
---
9
9
10
10
Apart from traditional push-based Helm deployments, you can use Codefresh for[GitOps deployments](https://codefresh.io/gitops/){:target="\_blank"} powered by Argo CD.
11
-
For an overview on GitOps, Argo CD, and how Codefresh implements both, see[Codefresh and GitOps]({{site.baseurl}}docs/getting-started/gitops-codefresh/).
11
+
For an overview on GitOps, Argo CD, and how Codefresh implements both, see[Codefresh and GitOps]({{site.baseurl}}/docs/getting-started/gitops-codefresh/).
12
12
13
13
14
14
Even though GitOps is not specific to Kubernetes, current GitOps tools work great with Kubernetes in the form of cluster controllers. The GitOps controller monitors the state of the Git repository, and when there is a commit, instructs the cluster to match the same state.
Copy file name to clipboardExpand all lines: _docs/dashboards/home-dashboard.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
@@ -134,7 +134,7 @@ Displays up to five of the most active applications and their current deployment
134
134
| Item| Description|
135
135
| ------------------------| ----------------|
136
136
|**Filter**| Filter applications by the clusters on which they are deployed, either by Cluster Name or by Cluster.|
137
-
|**View**| Click to go to the GitOps Apps dashboard. See[Monitoring GitOps applications]({{site.baseurl}}}}docs/deployments/gitops/applications-dashboard)|
137
+
|**View**| Click to go to the GitOps Apps dashboard. See[Monitoring GitOps applications]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard)|
138
138
|**Application Name**| The name of the application, and the names of the GitOps Runtime and the cluster on which it is deployed. Click the name to drill down into the application in the GitOps Apps dashboard.|
139
139
|**Health status**| The health status of the application, and can be either:{::nomarkdown}<ul><li>Healthy (green): The application is running on the cluster.</li><li>Degraded (red): The application failed to run.</li> <li>Rollback (yellow): There was a rollback to the previously deployed version.</li></ul> To see the breakdown by health status, mouse over the chart. <br> The number at the end of the bar is the total number of deployments for the application, and the percentage indicates the overall decrease or increase compared to the reference period. {:/}|
Copy file name to clipboardExpand all lines: _docs/installation/gitops/hybrid-gitops.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
@@ -1000,7 +1000,7 @@ Skip validating scopes for the token provided (for any Git provider). This flag
1000
1000
To skip token validation, add `--skip-permission-validation true`.
1001
1001
1002
1002
> IMPORTANT:
1003
-
Before using this flag, [review the required scopes for runtime tokens]({{site.baseurl}}/docs/reference//git-tokens/#git-runtime-token-scopes). <br><br>
1003
+
Before using this flag, [review the required scopes for runtime tokens]({{site.baseurl}}/docs/reference/git-tokens/#git-runtime-token-scopes). <br><br>
1004
1004
When defined, Codefresh does not validate the scopes assigned to the token provided. If the token does not include the scopes required for Codefresh to automatically create the repositories for the runtime and Git Source during installation, the installation will fail.
1005
1005
The alternative is to create both repos before the installation.
Copy file name to clipboardExpand all lines: _posts/2020-12-31-january-december-classic.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
@@ -9,7 +9,7 @@ description: "Changelog for Pipelines 2020 (Classic)"
9
9
- Codefresh will now use the default branch (e.g.`main`) instead of assuming`master`. This applies to GitHub, GitLab, and Bitbucket -[documentation]({{site.baseurl}}/docs/pipelines/steps/git-clone/)
10
10
- App-Proxy now supports GitLab -[documentation]({{site.baseurl}}/docs/installation/codefresh-runner/#app-proxy-installation)
11
11
- Helm promotion pipelines can be overridden in the GUI -[documentation]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion/#creating-a-custom-helm-board)
12
-
- Internal Registry mirror for the Codefresh runner -[documentation]({{site.baseurl}}/docs/installation/codefresh-runner//#configure-internal-registry-mirror)
12
+
- Internal Registry mirror for the Codefresh runner -[documentation]({{site.baseurl}}/docs/installation/codefresh-runner/#configure-internal-registry-mirror)
13
13
- Production and staging deployments guide -[documentation]({{site.baseurl}}/docs/ci-cd-guides/environment-deployments/)
14
14
- Escaping YAML in pipelines -[documentation]({{site.baseurl}}/docs/pipelines/what-is-the-codefresh-yaml/#escaping-strings)
15
15
- GitOps dashboard now shows affected services for each release -[documentation]({{site.baseurl}}/docs/ci-cd-guides/gitops-deployments/#working-with-the-gitops-dashboard)