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

Manage gitops runtime as argocd application#1354

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
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
4 changes: 2 additions & 2 deletions_docs/gitops-quick-start/quick-start-configure-runtime.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -35,8 +35,8 @@ Configuring the GitOps Runtime as an Argo CD Application enables:
* Monitoring health and sync statuses
* Enforcement of Git as the single source of truth

To configure, click **Configure as Argo CD Application**. Codefresh will automatically handle the setup—no further action required.

To configure, click **Configure as Argo CD Application**. Codefresh will automatically handle the setup—no further action required.
To manually install the runtime as an Argo CD application, visit [Managing GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/manage-runtimes/#manually-configuring-the-runtime-application).

## Add Git Source to Runtime

Expand Down
117 changes: 117 additions & 0 deletions_docs/installation/gitops/manage-runtimes.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -43,6 +43,123 @@ The Runtime's context menu now includes the **Runtime Application** option, whic
max-width="60%"
%}

Although this step is highly recommended, it’s not required. You can choose to:
* Skip this step and manage the runtime using your own deployment process (e.g., Helm), or
* Manually create your own Argo CD Application to manage the GitOps runtime.

---

## Manually Configuring the Runtime Application

### 1. Add the Chart and Values Files to Git

Start by adding the `gitops-runtime` Helm chart to your Git repository. Create both a `Chart.yaml` and a `values.yaml` file.

#### Chart.yaml
Replace `<Chart Version>` with the version of the chart you'd like to install.

```yaml
apiVersion: v2
name: codefresh-gitops-runtime
description: Codefresh GitOps Runtime umbrella chart
version: <Chart Version>
appVersion: 1.0.0
dependencies:
- name: gitops-runtime
repository: oci://quay.io/codefresh
version: <Chart Version>
```

[View the Helm Chart on ArtifactHub](https://artifacthub.io/packages/helm/codefresh-gitops-runtime/gitops-runtime){:target="_blank"}

---

#### values.yaml

Here's a basic example. Adjust it based on your setup:

```yaml
gitops-runtime:
argo-cd:
enabled: false

global:
codefresh:
accountId: <CODEFRESH_ACCOUNT_ID>
userToken:
secretKeyRef:
name: codefresh-user-token
key: token

external-argo-cd:
auth:
type: token
tokenSecretKeyRef:
name: gitops-runtime-argo-cd-token
key: token

runtime:
name: codefresh
isConfigurationRuntime: true
```

**Where to find these values:**
* **accountId:** [Account Settings → Account Information](https://g.codefresh.io/2.0/account-settings/account-information){:target="_blank"}
* **userToken:** [User Settings → Generate Token](https://g.codefresh.io/user/settings){:target="_blank"}
* **external Argo CD token:** Create via Argo CD CLI or UI if connecting to an external Argo CD instance.

> **Note:** Make sure not to commit any secret tokens to Git.

---

### 2. Create an Argo CD Application

Create an Argo CD Application that points to the Git repo where your runtime manifests are stored. We recommend storing this Application manifest in Git as well.

```yaml
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: <runtime-name>
labels:
codefresh.io/entity: runtime
codefresh.io/internal: 'true'
spec:
project: default
source:
repoURL: https://github.com/<owner>/<repo>.git
targetRevision: HEAD
path: <runtime-folder-path>
helm:
releaseName: <runtime-name>
destination:
namespace: runtime
server: https://kubernetes.default.svc
syncPolicy:
automated:
prune: true
selfHeal: true
allowEmpty: true
```

Ensure you include the following labels:
* `codefresh.io/entity: runtime`
* `codefresh.io/internal: 'true'`

---

### 3. (Optional) Manage This Application via Shared Configuration

We recommend managing the runtime Argo CD application as part of the Internal Shared Configuration (ISC). This ensures consistent configuration across all runtimes.

1. Go to [Account Settings → Account Information](https://g.codefresh.io/2.0/account-settings/account-information){:target="_blank"} and locate your Shared Configuration repository.
2. Navigate to `runtimes/<runtime-name>/in-cluster.yaml`.
3. Add the path to your runtime application's manifest under `source.directory.include`.

If your runtime app manifest is stored in a separate repository, you can:
* Add a second source (see [Argo CD multi-source applications](https://argo-cd.readthedocs.io/en/stable/user-guide/multiple-source-repositories/){:target="_blank"}), or
* Apply the manifest directly to the cluster without wrapping it in a parent application.

## Upgrade GitOps Runtimes

Upgrade provisioned Hybrid GitOps Runtimes to install critical security updates, new functionality, and the latest versions of all components.
Expand Down
2 changes: 2 additions & 0 deletions_docs/installation/gitops/runtime-configuration.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -64,6 +64,8 @@ Configuring the GitOps Runtime as an Argo CD Application ensures:
* **Visibility and monitoring**
The Runtime appears in the GitOps Apps dashboard, where you can monitor and manage it as any other Argo CD application.

To manually install the runtime as an Argo CD application, visit [Managing GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/manage-runtimes/#manually-configuring-the-runtime-application).

## Add Git Source to Runtime
A **Git Source** is a critical component in GitOps Runtimes, connecting a Git repository to the cluster, enabling deployment and configuration management of Argo CD applications.

Expand Down
1 change: 1 addition & 0 deletions_posts-gitops/2025-07-25-july-release-notes.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
../_posts/2025-07-25-july-release-notes.md
32 changes: 32 additions & 0 deletions_posts/2025-07-25-july-release-notes.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
---
title: "Release Notes: July 2025"
description: ""
---
## Features & enhancements
### GitOps: Runtime v0.22: Argo CD 3.0 Upgrade

This runtime release upgrades **Argo CD to version 3.0**, bringing the latest features and improvements to Codefresh GitOps.

While we haven't identified any breaking changes for standard Codefresh deployments, please review the following recommendations:

* If you have **customized any default Argo CD values** beyond what Codefresh distributes, you may be affected by changes introduced in Argo CD 3.0.
* Review the official [Argo CD 3.0 migration guide](https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.0-migration/) if you maintain custom configurations.
* If you have made **extensive customizations**, test this runtime upgrade in a **non-production environment first**.

For details, see the [runtime v0.22.1 release notes](https://github.com/codefresh-io/gitops-runtime-helm/releases/tag/0.22.1).



## Bug fixes
##### General
* Fixed an issue where Quick Search (CMD + K) did not return any GitOps-related items, including applications. Users can now search and access GitOps items directly through Quick Search as expected.
{% if page.collection == "posts" %}
##### Pipelines
* Fixed an issue that caused timeouts when loading UI pages for pipelines with a large number of triggers.
* Fixed an issue where MacOS builds failed with an 'Unauthorized' error when provisioning the runtime, preventing customers from running MacOS builds successfully.
* Fixed an issue where builds intermittently failed with a 'Failed to prepare dockerfile' error, preventing the Dockerfile from being fetched correctly during the build process.
* Fixed an issue where SaaS builds failed due to insufficient disk space by re-enabling cleanup processes.

##### GitOps
{% endif %}
* Fixed an issue where applications nested more than three layers deep were not displayed in the UI tree view. The full application hierarchy now appears correctly in the tree view.
[8]ページ先頭
©2009-2025 Movatter.jp