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: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,6 +151,10 @@ The ArgoHub home page and all pages within the ArgoHub collection are excluded f
151
151
- Commandbar HelpHub Search (managed via Commandbar Content Manager).
152
152
- Search engines that support the`noindex` rule, such as Google.
153
153
154
+
####Commandbar's HelpHub and Copilot Content Sync
155
+
156
+
Commandbar synchronizes the documentation site content using a crawler. However, the Auto Redirect mechanism prevents the crawler from accessing all Enterprise pages (see the "Auto Redirect from Enterprise to ArgoHub Collection" section for details). To address this issue, the Commandbar team configured the crawler to include the`cfdoctype` cookie, enabling it to access all documentation pages and bypass the redirect.
157
+
154
158
###Auto Redirect from Enterprise to ArgoHub Collection
155
159
156
160
When the GitOps client adds an ArgoHub system type cookie, the Documentation site will detect it and initiate an automatic redirect. If you open any page from the enterprise collection, the site will check for an equivalent document in the ArgoHub collection and redirect you there if one exists.
Copy file name to clipboardExpand all lines: _docs/administration/account-user-management/service-accounts.md
-10Lines changed: 0 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,16 +100,6 @@ max-width="90%"
100
100
|**Status**| Indicates if the service account is currently active (**Enabled**) or inactive (**Disabled**). You may want to disable a service account to invalidate its API keys without having to remove the service account, and simply reenable when needed.|
101
101
|**Actions**| The options available to manage the service account through its context menu: {::nomarkdown}<ul><li><b>Edit</b>: Modify the settings of the service account, including adding/removing teams, enabling/disabling admin role.</li><li><b>Delete</b>: Delete the service account, including all the API keys defined for the account. This means that actions through the Codefresh API or CLI that require these keys will fail.</li></ul>{:/}|
102
102
103
-
{% if page.collection != site.gitops_collection %}
104
-
##Authenticating to Amazon ECR with service account
105
-
106
-
Authenticate to Amazon ECR registries with credentials from the service account instead of the Access Key ID and Secret Access Key.
107
-
This allows pipelines to seamlessly authenticate to Amazon ECR via service account credentials, enhancing security and simplifying access management.
108
-
109
-
There are two requirements:
110
-
1. Set the option to authenticate via service accounts at the account level for pipelines. See[Advanced options for pipelines]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#advanced-options-for-pipelines).
111
-
1. Configure Amazon ECR integration to use service account credentials. See[Amazon ECR Container Registry pipeline integration]({{site.baseurl}}/docs/integrations/docker-registries/amazon-ec2-container-registry/).
112
-
{% endif %}
113
103
114
104
##Related articles
115
105
{% if page.collection != site.gitops_collection %}
Copy file name to clipboardExpand all lines: _docs/installation/gitops.md
+25-29Lines changed: 25 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,8 +11,8 @@ Managing applications at scale requires efficient tools and practices. Codefresh
11
11
#####What is a GitOps Runtime?
12
12
The GitOps Runtime is a specialized component installed within your cluster, acting as a bridge between your infrastructure and the Codefresh platform. It integrates seamlessly with Argo CD, a leading tool for continuous delivery, and Argo Rollouts for advanced deployment strategies.
13
13
14
-
This Runtime forms the foundation of your GitOps operations, enabling centralized control and visibility across multiple Argo CD instances.
15
-
By leveraging the Runtime, teams can efficiently orchestrate deployments, monitor environments, and ensure consistency across applications. To better understand how the Runtime manages key aspects like Git token usage and sharedconfig repos, see[GitOps Runtime concepts]({{site.baseurl}}/docs/installation/gitops/runtime-concepts/).
14
+
This Runtime forms the foundation of your GitOps operations, enabling centralized control and visibility across multiple Argo CD instances from a single control plane.
15
+
By leveraging the Runtime, teams can efficiently orchestrate deployments, monitor environments, and ensure consistency across applications. To better understand how the Runtime manages key aspects like Git token usage and sharedconfiguration, see[GitOps Runtime concepts]({{site.baseurl}}/docs/installation/gitops/runtime-concepts/).
16
16
17
17
{% include
18
18
image.html
@@ -50,13 +50,6 @@ No Argo CD yet? Deploy a new, fully managed instance of Argo CD with the GitOps
50
50
51
51
See[Install GitOps Runtime with new Argo CD]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/).
52
52
53
-
{% if page.collection != site.gitops_collection %}
54
-
#####Installation alongside Community Argo CD
55
-
Using Community Argo CD? Add Codefresh GitOps without disrupting your existing setup.
56
-
Requires additional configuration to manage resources separately and avoid interference with the existing Community Argo CD setup.
57
-
58
-
See[Install GitOps Runtime alongside Community Argo CD]({{site.baseurl}}/docs/installation/gitops/argo-with-gitops-side-by-side/).
59
-
{% endif %}
60
53
61
54
You can install one GitOps Runtime per cluster. To add more, each Runtime must be on a separate cluster and have a unique name.
62
55
@@ -74,27 +67,30 @@ The comparison below is provided for historical reference only.
74
67
The table below highlights the main differences between Hosted and Hybrid GitOps.
|**Ops**|**GitOps Apps**| Supported:<br>Deployment supported only on managed clusters<br>Self-healing interval: 90 seconds<br>See[Argo CD automatic self-healing](https://argo-cd.readthedocs.io/en/stable/user-guide/auto_sync/#automatic-self-healing){:target="\_blank"}| Supported:<br>Deployment supported on both in-cluster and managed clusters<br>Self-healing interval: 5 seconds (Argo CD default)<br>See[Argo CD automatic self-healing](https://argo-cd.readthedocs.io/en/stable/user-guide/auto_sync/#automatic-self-healing){:target="\_blank"}|
83
+
||**Environments**|Supported| Supported|
84
+
||**Products**|Supported| Supported|
85
+
||**Promotion Workflows**| Not supported| Supported|
Copy file name to clipboardExpand all lines: _docs/installation/gitops/hybrid-gitops-helm-installation.md
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,8 @@ This article describes how to install the GitOps Runtime in a Codefresh accounts
14
14
The Codefresh`values.yaml` located[here](https://github.com/codefresh-io/gitops-runtime-helm/blob/main/charts/gitops-runtime/){:target="\_blank"}, contains all the arguments you can configure, including optional ones.
15
15
Review how Codefresh[validates the Runtime's values.yaml]({{site.baseurl}}/docs/installation/gitops/gitops-values-yaml-validation/).
16
16
17
-
{% if page.collection != site.gitops_collection %}
18
-
To install the GitOps Runtime:
19
-
* With an existing Argo CD instance, see[Install GitOps Runtime with existing Argo CD]({{site.baseurl}}/docs/installation/gitops/runtime-install-with-existing-argo-cd/)
20
-
* Alongside your community Argo CD installation, see[Install GitOps Runtime alongside Community Argo CD]({{site.baseurl}}/docs/installation/gitops/argo-with-gitops-side-by-side/).
21
-
{% endif %}
17
+
To install the GitOps Runtime with an existing Argo CD instance, see[Install GitOps Runtime with existing Argo CD]({{site.baseurl}}/docs/installation/gitops/runtime-install-with-existing-argo-cd/).