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#764

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 1 commit intomasterfromfix-broken-links
Jul 13, 2023
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/ci-cd-guides/gitops-deployments.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -8,7 +8,7 @@ toc: true
---

Apart from traditional push-based Helm deployments, you can use Codefresh for [GitOps deployments](https://codefresh.io/gitops/){:target="\_blank"} powered by Argo CD.
For an overview on GitOps, Argo CD, and how Codefresh implements both, see [Codefresh and GitOps]({{site.baseurl}}docs/getting-started/gitops-codefresh/).
For an overview on GitOps, Argo CD, and how Codefresh implements both, see [Codefresh and GitOps]({{site.baseurl}}/docs/getting-started/gitops-codefresh/).


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.
Expand Down
2 changes: 1 addition & 1 deletion_docs/dashboards/home-dashboard.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -134,7 +134,7 @@ Displays up to five of the most active applications and their current deployment
| Item | Description |
| ------------------------| ---------------- |
|**Filter** | Filter applications by the clusters on which they are deployed, either by Cluster Name or by Cluster. |
|**View** | Click to go to the GitOps Apps dashboard. See [Monitoring GitOps applications]({{site.baseurl}}}}docs/deployments/gitops/applications-dashboard) |
|**View** | Click to go to the GitOps Apps dashboard. See [Monitoring GitOps applications]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard) |
|**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. |
|**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. {:/} |

Expand Down
2 changes: 1 addition & 1 deletion_docs/gitops-integrations/container-registries.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -85,7 +85,7 @@ use it.
## Related articles
[CI GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/)
[Issue-tracking GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/issue-tracking/)
[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration//)
[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)
[Images]({{site.baseurl}}/docs/dashboards/images/)
[Monitoring applications]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard/)

2 changes: 1 addition & 1 deletion_docs/installation/gitops/hybrid-gitops.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -1000,7 +1000,7 @@ Skip validating scopes for the token provided (for any Git provider). This flag
To skip token validation, add `--skip-permission-validation true`.

> IMPORTANT:
Before using this flag, [review the required scopes for runtime tokens]({{site.baseurl}}/docs/reference//git-tokens/#git-runtime-token-scopes). <br><br>
Before using this flag, [review the required scopes for runtime tokens]({{site.baseurl}}/docs/reference/git-tokens/#git-runtime-token-scopes). <br><br>
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.
The alternative is to create both repos before the installation.

Expand Down
2 changes: 1 addition & 1 deletion_posts/2019-12-31-january-december-classic.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -69,7 +69,7 @@ description: "Changelog for Pipelines 2019 (Classic)"
- SAML SSO support (Enterprise) - [documentation]({{site.baseurl}}/docs/administration/single-sign-on/saml/)
- Audit logs (Enterprise) - [documentation]({{site.baseurl}}/docs/administration/account-user-management/audit/)
- Checking out code with Subversion, HG, Perforce etc. - [documentation]({{site.baseurl}}/docs/example-catalog/ci-examples/non-git-checkout/)
- Migrating to explicit git clone steps - [documentation]({{site.baseurl}}docs/pipelines/steps/git-clone/)
- Migrating to explicit git clone steps - [documentation]({{site.baseurl}}/docs/pipelines/steps/git-clone/)
- Custom annotations on projects, pipelines, builds - [documentation]({{site.baseurl}}/docs/pipelines/annotations/)
- Deployments with Pulumi - [documentation]({{site.baseurl}}/docs/example-catalog/cd-examples/pulumi/)
- Deployments with Terraform - [documentation]({{site.baseurl}}/docs/example-catalog/cd-examples/terraform/)
Expand Down
2 changes: 1 addition & 1 deletion_posts/2020-12-31-january-december-classic.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -9,7 +9,7 @@ description: "Changelog for Pipelines 2020 (Classic)"
- 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/)
- App-Proxy now supports GitLab - [documentation]({{site.baseurl}}/docs/installation/codefresh-runner/#app-proxy-installation)
- Helm promotion pipelines can be overridden in the GUI - [documentation]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion/#creating-a-custom-helm-board)
- Internal Registry mirror for the Codefresh runner - [documentation]({{site.baseurl}}/docs/installation/codefresh-runner//#configure-internal-registry-mirror)
- Internal Registry mirror for the Codefresh runner - [documentation]({{site.baseurl}}/docs/installation/codefresh-runner/#configure-internal-registry-mirror)
- Production and staging deployments guide - [documentation]({{site.baseurl}}/docs/ci-cd-guides/environment-deployments/)
- Escaping YAML in pipelines - [documentation]({{site.baseurl}}/docs/pipelines/what-is-the-codefresh-yaml/#escaping-strings)
- GitOps dashboard now shows affected services for each release - [documentation]({{site.baseurl}}/docs/ci-cd-guides/gitops-deployments/#working-with-the-gitops-dashboard)
Expand Down
[8]ページ先頭
©2009-2025 Movatter.jp