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

Remove community argo content#1281

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 3 commits intomasterfromgitops-runtime-side-by-side-option-cleanup
Apr 10, 2025
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
11 changes: 2 additions & 9 deletions_docs/installation/gitops.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -11,8 +11,8 @@ Managing applications at scale requires efficient tools and practices. Codefresh
##### What is a GitOps Runtime?
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.

This Runtime forms the foundation of your GitOps operations, enabling centralized control and visibility across multiple Argo CD instances.
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/).
This Runtime forms the foundation of your GitOps operations, enabling centralized control and visibility across multiple Argo CD instances from a single control plane.
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/).

{% include
image.html
Expand DownExpand Up@@ -50,13 +50,6 @@ No Argo CD yet? Deploy a new, fully managed instance of Argo CD with the GitOps

See [Install GitOps Runtime with new Argo CD]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/).

{% if page.collection != site.gitops_collection %}
##### Installation alongside Community Argo CD
Using Community Argo CD? Add Codefresh GitOps without disrupting your existing setup.
Requires additional configuration to manage resources separately and avoid interference with the existing Community Argo CD setup.

See [Install GitOps Runtime alongside Community Argo CD]({{site.baseurl}}/docs/installation/gitops/argo-with-gitops-side-by-side/).
{% endif %}

You can install one GitOps Runtime per cluster. To add more, each Runtime must be on a separate cluster and have a unique name.

Expand Down
8 changes: 0 additions & 8 deletions_docs/installation/gitops/gitops-runtime.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -50,14 +50,6 @@ No Argo CD yet? Deploy a new, fully managed instance of Argo CD with the GitOps

See [Install GitOps Runtime with new Argo CD]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/).

{% if page.collection != site.gitops_collection %}
##### Installation alongside Community Argo CD
Using Community Argo CD? Add Codefresh GitOps without disrupting your existing setup.
Requires additional configuration to manage resources separately and avoid interference with the existing Community Argo CD setup.

See [Install GitOps Runtime alongside Community Argo CD]({{site.baseurl}}/docs/installation/gitops/argo-with-gitops-side-by-side/).
{% endif %}

You can install one GitOps Runtime per cluster. To add more, each Runtime must be on a separate cluster and have a unique name.


Expand Down
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -14,11 +14,8 @@ This article describes how to install the GitOps Runtime in a Codefresh accounts
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.
Review how Codefresh [validates the Runtime's values.yaml]({{site.baseurl}}/docs/installation/gitops/gitops-values-yaml-validation/).

{% if page.collection != site.gitops_collection %}
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/)
* 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/).
{% endif %}
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/).




Expand Down
1 change: 0 additions & 1 deletion_docs/installation/gitops/runtime-architecture.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -306,5 +306,4 @@ The GitOps Runtime reports data to the Codefresh platform, which stores the data
## Related articles
[Install GitOps Runtime with existing Argo CD]({{site.baseurl}}/docs/installation/gitops/runtime-install-with-existing-argo-cd/)
[Install GitOps Runtime with new Argo CD]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/)
[Install GitOps Runtime alongside Community Argo CD]({{site.baseurl}}/docs/installation/gitops/argo-with-gitops-side-by-side/)
{% if page.collection != site.gitops_collection %}[On-premises GitOps Runtime installation]({{site.baseurl}}/docs/installation/gitops/on-prem-gitops-runtime-install/){% endif %}
2 changes: 1 addition & 1 deletion_docs/installation/gitops/runtime-concepts.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -87,4 +87,4 @@ For information on adding clusters and managing them, see [Managing external clu
[Runtime prerequisites ]({{site.baseurl}}/docs/installation/gitops/runtime-prerequisites/)
[Install GitOps Runtime with existing Argo CD]({{site.baseurl}}/docs/installation/gitops/runtime-install-with-existing-argo-cd/)
[Install GitOps Runtime with new Argo CD]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/)
{% if page.collection != site.gitops_collection %}[Install GitOps Runtime alongside Community Argo CD]({{site.baseurl}}/docs/installation/gitops/argo-with-gitops-side-by-side/){% endif %}

View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -668,6 +668,6 @@ providers:
```

## Related articles
[System requirements & prerequisites]({{site.baseurl}}/docs/installation/gitops/runtime-system-requirements/)
[Install GitOps Runtime]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/)
[Install GitOps Runtimealongside Community Argo CD]({{site.baseurl}}/docs/installation/gitops/argo-with-gitops-side-by-side/)
[Runtime prerequisites]({{site.baseurl}}/docs/installation/gitops/runtime-system-requirements/)
[Install GitOps Runtime with existing Argo CD]({{site.baseurl}}/docs/installation/gitops/runtime-install-with-existing-argo-cd/)
[Install GitOps Runtimewith new Argo CD]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/)
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -12,18 +12,17 @@ In addition to the tunnel-based access mode which is is the default, the GitOps
The ingress controller configured on the same Kubernetes cluster as the GitOps Runtime, implements the ingress traffic rules for the GitOps Runtime.
* **Service-mesh based access mode**
The runtime integrates with a service mesh for communication.
For details, see [GitOps Runtime architecture]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/).
For details, see [GitOps Runtime architecture]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/).

##### Pre-installation configuration
Configure ingress controllers and service meshes before installing the GitOps Runtime.
Configure ingress controllers and service meshes before installing the GitOps Runtime. See [Pre-installation: Configure ingress controllers/service meshes](#pre-installation-configure-ingress-controllersservice-meshes).

##### Installation command flags
The Runtime Install command requires additional flags to specify ingress or service-mesh compatibility.
If you are installing alongside Community Argo CD, the Runtime Install command requires additional flags.
The Runtime Install command requires additional flags to specify ingress or service-mesh compatibility. See [Install Runtime command for ingress-based/service-mesh based access modes](#installation-install-runtime-command-for-ingress-basedservice-mesh-based-access-modes).


##### Post-installation configuration
After installing the GitOps Runtime, specific ingress controllers and service meshes need additional configuration.
After installing the GitOps Runtime, specific ingress controllers and service meshes need additional configuration. See [Post-installation: Configure ingress controllers/service meshes](#post-installation-configure-ingress-controllersservice-meshes).


## Pre-installation: Configure ingress controllers/service meshes
Expand All@@ -47,23 +46,13 @@ Following are the additional flags you need to add to the install command for in
--set global.runtime.ingress.enabled=true \
--set "global.runtime.ingress.hosts[0]"=<ingress-host> \
--set global.runtime.ingress.className=<ingress-class> \
{% if page.collection != site.gitops_collection %}
--set argo-cd.fullnameOverride=codefresh-argo-cd \
--set argo-rollouts.fullnameOverride=codefresh-argo-cd \
--set argo-cd.configs.cm.application.resourceTrackingMethod=annotation+label \
{% endif %}
{% endhighlight %}

where:
* `global.runtime.ingress.enabled=true`is mandatory for ingress-based Runtimes. Indicates the runtime is ingress-based.
* `<ingress-host>` is the IP address or hostname of the ingress controller. Mandatory for ingress-based Runtimes.
* `<ingress-class>` is the ingress class of the ingress controller (e.g., `nginx` for the NGINX ingress controller). Mandatory for ingress-based Runtimes.
{% if page.collection != site.gitops_collection %}
**Community Argo CD only**
* `argo-cd.fullnameOverride=codefresh-argo-cd` is _mandatory_ to avoid conflicts at the cluster-level for resources in both the Community Argo CD and GitOps Runtime's Argo CD.
* `argo-rollouts.fullnameOverride=codefresh-argo-rollouts` is _mandatory_ when you have Argo Rollouts in your cluster to avoid conflicts.
* `argo-cd.configs.cm.application.resourceTrackingMethod=annotation+label` is _mandatory_ to avoid conflicts when tracking resources with the same application names or when tracking the same resource in both the Community Argo CD and GitOps Runtime's Argo CD.
{% endif %}


### Service-mesh-based install command (without ingress and tunnel)
Following are the additional flags you need to add to the install command for service-mesh based access modes.
Expand All@@ -72,24 +61,13 @@ Following are the additional flags you need to add to the install command for se
--set global.runtime.ingressUrl=<ingress-url> \
--set global.runtime.ingress.enabled=false \
--set tunnel-client.enabled=false \
{% if page.collection != site.gitops_collection %}
--set argo-cd.fullnameOverride=codefresh-argo-cd \
--set argo-rollouts.fullnameOverride=codefresh-argo-cd \
--set argo-cd.configs.cm.application.resourceTrackingMethod=annotation+label \
{% endif %}

{% endhighlight %}

where:
* `global.runtime.ingressUrl=<ingress-url>` is the ingress URL that serves as the entry point to the cluster.
* `global.runtime.ingress.enabled=false` explicitly disables ingress-based access mode.
* `tunnel-client.enabled=false` explicitly disables tunnel-based access mode.
{% if page.collection != site.gitops_collection %}
**Community Argo CD only**
* `argo-cd.fullnameOverride=codefresh-argo-cd` is _mandatory_ to avoid conflicts at the cluster-level for resources in both the Community Argo CD and GitOps Runtime's Argo CD.
* `argo-rollouts.fullnameOverride=codefresh-argo-rollouts` is _mandatory_ when you have Argo Rollouts in your cluster to avoid conflicts.
* `argo-cd.configs.cm.application.resourceTrackingMethod=annotation+label` is _mandatory_ to avoid conflicts when tracking resources with the same application names or when tracking the same resource in both the Community Argo CD and GitOps Runtime's Argo CD.
{% endif %}


## Post-installation: Configure ingress controllers/service meshes
Required only for ALB AWS and NGINX Enterprise ingress-controllers, and Istio service meshes.<br>
Expand All@@ -102,5 +80,6 @@ Required only for ALB AWS and NGINX Enterprise ingress-controllers, and Istio se

## Related articles
[GitOps Runtime architecture]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/)
[Runtime prerequisites]({{site.baseurl}}/docs/installation/gitops/runtime-system-requirements/)
[Install GitOps Runtime with existing Argo CD]({{site.baseurl}}/docs/installation/gitops/runtime-install-with-existing-argo-cd/)
[Install GitOps Runtime with new Argo CD]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/)
Loading
[8]ページ先頭
©2009-2025 Movatter.jp