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

Commitfa1722f

Browse files
Update runtime-architecture.md (#1194)
* Update runtime-architecture.mdAdded runtime data flow and reported data* Update _docs/installation/gitops/runtime-architecture.mdCo-authored-by: Zhenya Tikhonov <zhenya.tikhonov@octopus.com>* Update runtime-architecture.md---------Co-authored-by: Zhenya Tikhonov <zhenya.tikhonov@octopus.com>
1 parent9a77c44 commitfa1722f

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed

‎_docs/installation/gitops/runtime-architecture.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -223,6 +223,33 @@ The customer environment that communicates with the GitOps Runtime and Codefresh
223223
Organizational Systems include the customer's tracking, monitoring, notification, container registries, Git providers, and other systems. They can be entirely on-premises or in the public cloud.
224224
Either the ingress controller (ingress-based hybrid environments), or the Tunnel Client (tunnel-based hybrid environments), forwards incoming events to the GitOps Application Proxy.
225225

226+
##Data flow: GitOps Runtime & external systems
227+
The GitOps Runtime interacts with external systems and components in the customer environment to enable GitOps operations and processes.
228+
229+
***Runtime cluster**
230+
* Both Argo CD and Codefresh components within the Runtime interact with the Runtime cluster’s Kubernetes API server.
231+
* Argo CD components also access managed clusters registered to GitOps Runtimes to deploy applications.
232+
233+
***Git providers**
234+
* Argo CD components access Git providers such as GitHub. Git provider credentials are always securlety stored in the customer’s cluster.
235+
* Codefresh components also access the Git provider to enable UI-driven commits and pull requests.
236+
237+
***Container registries and Jira (optional)**
238+
If enrichment functionality is enabled, jobs can be executed within the Runtime cluster or a CI system to retrieve metadata from those container registries and Jira instances integrated with Codefresh.
239+
240+
241+
##Data reporting: GitOps Runtime to Codefresh Platform
242+
The GitOps Runtime reports data to the Codefresh platform, which stores the data.
243+
244+
{: .table .table-bordered .table-hover}
245+
| Entity/Metadata| Reported data|
246+
| --------------| --------------|
247+
|**Kubernetes resources**| {::nomarkdown}<ul><li>Argo CD applications</l><li>All managed resources within an Argo CD application, for example, Deployments, ConfigMaps</li><li>Argo Rollouts and ReplicaSets</li></ul>{:/}|
248+
|**Git commit metadata**| {::nomarkdown}<ul><li>Commit SHA, message, and committer details (avatar URL, username)</l><li>Link to the commit in the Git provider</li></ul>{:/}|
249+
|**Jira issue metadata**| {::nomarkdown}<ul><li>Jira ticket number, link, and title (if configured)</l></ul>{:/}|
250+
|**Docker image metadata**| {::nomarkdown}<ul><li>Image name, digest, and repository information (if configured)</l></ul>{:/}|
251+
252+
226253

227254
##Related articles
228255
<!--- [Hosted GitOps Runtime installation]({{site.baseurl}}/docs/installation/gitops/hosted-runtime/)-->

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp