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

Commitef5b352

Browse files
committed
Update architecture
Fixed GitOps and runner firewall architecture diagrams
1 parentf0479be commitef5b352

20 files changed

+1724
-111
lines changed

‎_docs/getting-started/intro-to-codefresh.md‎

Lines changed: 64 additions & 77 deletions
Original file line numberDiff line numberDiff line change
@@ -5,115 +5,102 @@ group: getting-started
55
toc:true
66
---
77

8-
TBD
9-
What is Codefresh?
10-
11-
The short answer: Complete CI/CD and GitOps-powered Argo CD in the same product.
12-
13-
Now for the long answer.
8+
What is Codefresh? A complete CI/CD and GitOps-powered Argo CD in the same product.
149

1510
##Codefresh & CI/CD
1611

17-
Codefresh is a_complete CI/CD solution_, not just CI.
18-
We cover the full software lifecycle. View a release in the Kubernetes dashboard, click on it and go to the Docker image, click on the Docker image and go to the build that created it, all from a single interface.
19-
20-
Codefresh is turbo-charged CI/CD!
21-
22-
We work with all major Git platforms and cloud providers. There is no lock-in with any particular vendor. Unlike other CI/CD platforms which can be tightly coupled to a single Git provider, or a specific vendor or set of tools, Codefresh supports a fully programmtic implementation.
23-
24-
Everything in the pipeline is defined as code and applied with the command line. Storing the definitions in a code repo ensures consistenct. Upscaling or expanind Doing so means we can create all of our pipelines in a consistent way and store those definitions in a code repository. Taking this one step step deeper, we could then create a bootstrap pipeline in Codefresh that generates pipelines when new definitions are added to this repo. See our previous post Programmatic Creation of Codefresh Pipelines (part 2) for more on this.
25-
26-
Has pipelines with Has several unique features such as a distributed Docker layer cache, an auto-mounted shared volume, a private Docker registry and a private Helm repository.
27-
* Built-in Kubernetes and Helm dashboards
28-
* Helm charts browser, and Helm environment board
29-
30-
31-
32-
33-
How does Codefresh do it?
34-
Everything for CI/CD in Codefresh starts and ends with pipelines. In Codefresh, a pipeline can do pretty much anyhting, only CI, only CD, both CI and CD.
35-
36-
37-
38-
39-
40-
41-
Completely programmatic approach
42-
Pipelines are create pipelines and define the pipeline’s steps, triggers, and variables.
12+
Codefresh is a cloud-native continuous integration and delivery platform that enables teams to quickly and efficiently develop, deploy, and manage cloud-native applications. Teams can quickly and easily build, test, and deploy their applications on any cloud platform, including Kubernetes, Docker, and AWS. With its robust automation capabilities and powerful integrations, teams can easily collaborate and quickly deliver high-quality software. Our intuitive, easy-to-use UI helps streamline the development process.
4313

4414

4515

16+
Codefresh is a_complete CI/CD solution_, not just CI, covering the full software lifecycle.
17+
View a release in the Kubernetes dashboard, click on the release to go to the Docker image, click on the Docker image to go to the build that created it, all from a single interface. !
4618

47-
The Docker registry integrationsandall cluster integrations are automatically available to all pipelines. You don’t need docker login commands or kubectl commands toset up a Kube context inside your pipeline.
19+
Codefresh works with all major Git platformsandcloud providers. There is no lock-in with any particular vendor. Unlike other CI/CD platforms which can be tightly coupled toa single Git provider, or a specific vendor or set of tools, Codefresh supports a fully programmtic implementation.
4820

4921

5022

51-
Pipelines can Run unit tests, integration tests, acceptance tests etc.
23+
###CI/CD pipelines
5224

25+
Everything in Codefresh CI/CD starts and ends with pipelines.
26+
A Codefresh pipeline has two distinct aspects, specifications that define the pipeline, and steps that are essentially a collection of Docker images that define the jobs and CI and CD processes to implement.
27+
28+
To see how pipeline work, start with the[Introduction to Codefresh pipelines]({{site.baseurl}}/docs/configure-ci-cd-pipeline/introduction-to-codefresh-pipelines/), or jump to[pipeline creation]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/).
5329

30+
For ready-to-use collections of pipeline steps, check out our[Plugin marketplace](https://codefresh.io/steps/){:target="\_blank"}
5431

32+
###Integrations
33+
For a seamless CI/CD experience, Codefresh has native integrations with almost every major provider.
34+
Easily connect Git providers, registry providers, storage providers, secret stores, and notification channels.
35+
Docker registry and all cluster integrations are automatically available to all pipelines. You don’t need Docker login commands or`kubectl` commands to set up a Kube context inside your pipeline.
5536

37+
Look for Pipeline Integrations in the documentation.
5638

57-
Pipeline extras
58-
We support all Git providers: Both on-premises and cloud
59-
provides a rich set of triggers: Trigger pipelines on a schedule, from a push to a docker registry or from a push to a helm registry or from actions that happened in Git.
60-
Has a rich, modern API With Codefresh, you can trigger a pipeline
39+
###Dashboards and insights
40+
Dashboards are key to providing the right information at the right time.
41+
Codefresh has dedicated dashboards for Helm and Kubernetes, and another dashboard that combines Helm and Kubernetes information in the same location.
6142

62-
Since Codefresh is decoupled from any single pipeline source, we provide a programmatic way to
43+
* Helm Boards
44+
A special environment dashboard to track your applications as they move within your infrastructure (e.g., Dev, QA, Prod), and shift Helm releases between environments.
6345

46+
* Helm Releases
47+
Here's where you can see everything about the cluster, including current status, currently deployed releases, their previous revisions including change tracking, and even rollbacks.
6448

65-
##CI/CD pipelines
49+
* Kubernetes Services
50+
Track the state of your Kubernetes clusters, and even manage services if you have the appropriate access privileges.
6651

67-
As mentioned earlier, everything in Codefresh CI/CD starts and ends with pipelines.
68-
A Codefresh pipeline has two distinct aspects:
52+
* Environment Dashboard
53+
For both Kubernetes and Helm releases, see cluster status and pipeline information.
6954

70-
* Pipeline specifications
71-
Specifications define the pipeline:
72-
* Metadata such as name, project, tags, in Codefresh
73-
* Events that trigger the pipeline, such as webhooks, cron events, etc.
74-
* Steps to use for this pipeline (inline, from a repo, etc.)
7555

76-
* Pipeline steps
77-
Pipeline steps are essentially a collection of Docker images that define the:
78-
* Jobs to run
79-
* Sequence in which to run the jobs
80-
* CI and CD processes to implement
56+
###Where to go from here
57+
Here are several useful links to further explore CI/CD with Codefresh:
8158

82-
Step types range from clone, build, deploy, and, a freestyle step when no size fits.
83-
For ready-to-use collections of pipeline steps, check out our[Plugin marketplace](https://codefresh.io/steps/){:target="\_blank"}
59+
**Quick starts**
60+
To get up and running, follow our quick starts. The quick start modules are a series of flows that guide you from setting up your first account in Codefresh, to creating a basic pipeline, and deploying to Kubernetes.
61+
See[CI/CD quick starts]({{site.baseurl}}/docs/quick-start/ci-quick-start/).
8462

63+
**Example catalog**
64+
If you are familiar with CI/CD, we have an extensive collection of examples that cover several CI and CD scenarios:
65+
[CI examples]({{site.baseurl}}/docs/example-catalog/ci-examples/)
66+
[CD examples]({{site.baseurl}}/docs/example-catalog/cd-examples/)
8567

68+
**Guides**
69+
And finally, if you want more meat, dive in to our detailed guides. Look for CI/CI guides in the documentation.
8670

87-
To see how pipeline work, start with the[Introduction to Codefresh pipelines]({{site.baseurl}}/docs/configure-ci-cd-pipeline/introduction-to-codefresh-pipelines/), or jump to[pipeline creation]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/).
8871

89-
##Releases and dashboards
90-
Dashboards are key to providing information at the right time.
91-
perational Dashboards ~ Exposing the most commonly needed application and environmental information to developers so that they can troubleshoot without needing assistance from the DevOps teams; even in production
72+
##Codefresh & GitOps with Argo CD
9273

93-
Analytical Dashboards ~ Developers often need to reach out to the DevOps team to get statistics and metrics around builds and deployments. Codefresh automatically generates DORA metrics as well as many other key indicators of build and deployment efficiency, which can be easily viewed in seconds by product owners and management alike.
74+
GitOps provides a way to manage cloud-native applications using Git as the source of truth. Teams can define the desired state of their applications and Kubernetes clusters in a Git repository and then automatically deploy the applications to Kubernetes clusters.
75+
Codefresh is a full-featured, turn-key solution for application deployments and releases. Powered by Argo, Codefresh uses Argo CD, Argo Workflows, Argo Events, and Argo Rollouts, extended with unique functionality and features essential for enterprise deployments. By combining GitOps with Codefresh, teams can create Argo Workflows and Argo Applications to seamlessly build, test, and deploy their applications.
9476

95-
###Integrations
96-
For a seamless CI/CD experience, Codefresh has native integrations with alomst every major provider.
97-
Easily connect Git providers, registry providers, storage providers, secret stores, and notification channels
9877

99-
Docker registry and all cluster integrations are automatically available to all pipelines. You don’t need Docker login commands or`kubectl` commands to set up a Kube context inside your pipeline.
78+
GitOps Runtimes
79+
Install Hosted or Hybrid GitOp R
10080

101-
Go to Pipeline Integrations in the UI, and see how to
102-
###Where to go from here
103-
Here are several links we think wouuld be useful t
81+
Codefresh offers security, maintainability, traceability, and most importantly, a single control plane for all stakeholders, be they developers, operators, product owners or project managers.
10482

105-
Quick starts
106-
To get up and running, follow our quick starts. The quick start modules are a series of flows that guide you from setting up your first account in Codefresh, to creating a basic pipeline, and deploying to Kubernetes.
107-
See XREF TBD
83+
Codefresh brings the power of the Argo project to your Kubernetes deployments:
10884

109-
Example catalog
110-
For those who are familiar with CI/CD, we have an extensive collection of examples, covering several CI and CD scenarios:
111-
[CI examples]({{site.baseurl}}/docs/example-catalog/ci-examples/)
112-
[CD examples]({{site.baseurl}}/docs/example-catalog/cd-examples/)
85+
Argo CD for declarative continuous deployment
86+
Argo Rollouts for progressive delivery
87+
Argo Workflows as the workflow engine
88+
Argo Events for event-driven workflow automation framework
89+
Codefresh creates a conformed fork of the Argo project, providing an enterprise-supported version of the same, enhanced with unique functionality.
11390

114-
Guides
115-
And finally, if you want more meat, dive in to our detailed guides.
116-
XREF TBD
91+
Our users rely on the Codefresh platform to deliver software, reliably and predictably, without disruptions.
92+
To maintain that high standard, we add several weeks of testing and bug fixes to new versions of Argo before making them available within Codefresh. Typically, new versions of Argo are available within 30 days of their release.
11793

118-
##Codefresh & GitOps with Argo CD
94+
Deliver software at scale by managing hundreds or thousands of deployment targets and applications
95+
Get a secure, enterprise-ready distribution of Argo with built-in identity, RBAC (role-based access control), and secrets
96+
Gain clear visibility across all deployments and trace changes and regressions from code to cloud in seconds
97+
Get enterprise-level dedicated support for Argo deployments
98+
Get insights into every aspect of your CI/CD with smart dashboards
99+
Manage multiple runtimes and multiple clusters in a single pane of glass
100+
###Dashboards
101+
Dashboards are key to providing the right information at the right time.
102+
Operational Dashboards
103+
Exposing the most commonly needed application and environmental information to developers so that they can troubleshoot without needing assistance from the DevOps teams; even in production
119104

105+
Analytical Dashboards
106+
Developers often need to reach out to the DevOps team to get statistics and metrics around builds and deployments. Codefresh automatically generates DORA metrics as well as many other key indicators of build and deployment efficiency, which can be easily viewed in seconds by product owners and management alike.

‎_docs/installation/behind-the-firewall.md‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,8 @@ Here is the overall architecture:
2323

2424
{% include image.html
2525
lightbox="true"
26-
file="/images/administration/behind-the-firewall/architecture.png"
27-
url="/images/administration/behind-the-firewall/architecture.png"
26+
file="/images/runtime/behind-the-firewall/architecture.png"
27+
url="/images/runtime/behind-the-firewall/architecture.png"
2828
alt="Codefresh Hybrid CD/CD behind the firewall"
2929
caption="Codefresh Hybrid CD/CD behind the firewall"
3030
max-width="100%"
@@ -80,8 +80,8 @@ need to mark it as *behind the firewall* as well:
8080

8181
{% include image.html
8282
lightbox="true"
83-
file="/images/administration/behind-the-firewall/behind-the-firewall-toggle.png"
84-
url="/images/administration/behind-the-firewall/behind-the-firewall-toggle.png"
83+
file="/images/runtime/behind-the-firewall/behind-the-firewall-toggle.png"
84+
url="/images/runtime/behind-the-firewall/behind-the-firewall-toggle.png"
8585
alt="Behind the firewall toggle"
8686
caption="Behind the firewall toggle"
8787
max-width="100%"
@@ -92,8 +92,8 @@ the Codefresh SAAS doesn't have access to your on-premises GIT repository.
9292

9393
{% include image.html
9494
lightbox="true"
95-
file="/images/administration/behind-the-firewall/behind-the-firewall-tag.png"
96-
url="/images/administration/behind-the-firewall/behind-the-firewall-tag.png"
95+
file="/images/runtime/behind-the-firewall/behind-the-firewall-tag.png"
96+
url="/images/runtime/behind-the-firewall/behind-the-firewall-tag.png"
9797
alt="Behind the firewall tags"
9898
caption="Behind the firewall tags"
9999
max-width="100%"
@@ -150,8 +150,8 @@ Once you select your GIT provider, you need to manually enter your username and
150150

151151
{% include image.html
152152
lightbox="true"
153-
file="/images/administration/behind-the-firewall/enter-repo-details.png"
154-
url="/images/administration/behind-the-firewall/enter-repo-details.png"
153+
file="/images/runtime/behind-the-firewall/enter-repo-details.png"
154+
url="/images/runtime/behind-the-firewall/enter-repo-details.png"
155155
alt="Entering repository details"
156156
caption="Entering repository details"
157157
max-width="60%"
@@ -163,8 +163,8 @@ Once that is done, Codefresh will show you the webhook endpoint along with a sec
163163

164164
{% include image.html
165165
lightbox="true"
166-
file="/images/administration/behind-the-firewall/codefresh-webhook.png"
167-
url="/images/administration/behind-the-firewall/codefresh-webhook.png"
166+
file="/images/runtime/behind-the-firewall/codefresh-webhook.png"
167+
url="/images/runtime/behind-the-firewall/codefresh-webhook.png"
168168
alt="Codefresh webhook details"
169169
caption="Codefresh webhook details"
170170
max-width="60%"
@@ -228,8 +228,8 @@ To connect a cluster that is behind the firewall follow the [connecting cluster
228228

229229
{% include image.html
230230
lightbox="true"
231-
file="/images/administration/behind-the-firewall/cluster-behind-firewall.png"
232-
url="/images/administration/behind-the-firewall/cluster-behind-firewall.png"
231+
file="/images/runtime/behind-the-firewall/cluster-behind-firewall.png"
232+
url="/images/runtime/behind-the-firewall/cluster-behind-firewall.png"
233233
alt="Marking a Kubernetes cluster as internal"
234234
caption="Marking a Kubernetes cluster as internal"
235235
max-width="60%"

‎_docs/installation/installation-options.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -132,10 +132,10 @@ For the architecture, see [Hosted GitOps Runtime architecture]({{site.baseurl}}/
132132
{% include
133133
image.html
134134
lightbox="true"
135-
file="/images/runtime/intro-hosted-hosted-initial-view.png"
136-
url="/images/runtime/intro-hosted-hosted-initial-view.png"
137-
alt="Hosted runtime setup"
138-
caption="Hosted runtime setup"
135+
file="/images/runtime/hosted-gitops-initial-view.png"
136+
url="/images/runtime/hosted-gitops-initial-view.png"
137+
alt="HostedGitOpsruntime setup"
138+
caption="HostedGitOpsruntime setup"
139139
max-width="80%"
140140
%}
141141

@@ -195,7 +195,7 @@ The table below highlights the main differences between Hosted and Hybrid GitOps
195195
||Image enrichment| Supported| Supported|
196196
|| Rollouts| Supported| Supported|
197197
|Integrations|| Supported| Supported|
198-
|Dashboards|Home Analytics| Hosted runtime and deployments|Runtimes, deployments, Delivery Pipelines|
198+
|Dashboards|GitOps Overview| Hosted runtime and deployments|Runtimes, deployments, Delivery Pipelines|
199199
||DORA metrics| Supported|Supported|
200200
||Applications| Supported|Supported|
201201

‎_docs/installation/runtime-architecture.md‎

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ group: installation
55
toc:true
66
---
77

8-
If you have familiarized yourself with the different installation options, here's a deep dive into the architecture and components ofeach.
8+
If you have familiarized yourself with the different installation options, here's a deep dive into the architecture and components ofthe different options.
99

1010
##Runner architecture
1111

@@ -59,10 +59,10 @@ The diagram shows a high-level view of the GitOps environment, and its core comp
5959
{% include
6060
image.html
6161
lightbox="true"
62-
file="/images/getting-started/architecture/arch-codefresh-simple.png"
63-
url="/images/getting-started/architecture/arch-codefresh-simple.png"
64-
alt="Codefresh GitOpsPlatform architecture"
65-
caption="Codefresh GitOpsPlatform architecture"
62+
file="/images/runtime/architecture/arch-codefresh-simple.png"
63+
url="/images/runtime/architecture/arch-codefresh-simple.png"
64+
alt="Codefresh GitOpsplatform architecture"
65+
caption="Codefresh GitOpsplatform architecture"
6666
max-width="100%"
6767
%}
6868

@@ -116,10 +116,10 @@ In the hosted environment, the Codefresh Runtime is installed on a K8s cluster m
116116
{% include
117117
image.html
118118
lightbox="true"
119-
file="/images/getting-started/architecture/arch-hosted.png"
120-
url="/images/getting-started/architecture/arch-hosted.png"
121-
alt="Hostedruntime architecture"
122-
caption="Hostedruntime architecture"
119+
file="/images/runtime/architecture/arch-hosted.png"
120+
url="/images/runtime/architecture/arch-hosted.png"
121+
alt="HostedGitOps Runtime architecture"
122+
caption="HostedGitOps Runtime architecture"
123123
max-width="100%"
124124
%}
125125

@@ -129,10 +129,10 @@ Tunnel-based Hybrid GitOps runtimes use tunneling instead of ingress controllers
129129
{% include
130130
image.html
131131
lightbox="true"
132-
file="/images/getting-started/architecture/arch-hybrid-ingressless.png"
133-
url="/images/getting-started/architecture/arch-hybrid-ingressless.png"
134-
alt="Tunnel-basedhybrid runtime architecture"
135-
caption="Tunnel-basedhybrid runtime architecture"
132+
file="/images/runtime/architecture/arch-hybrid-ingressless.png"
133+
url="/images/runtime/architecture/arch-hybrid-ingressless.png"
134+
alt="Tunnel-basedHybrid GitOps Runtime architecture"
135+
caption="Tunnel-basedHybrid GitOps Runtime architecture"
136136
max-width="100%"
137137
%}
138138

@@ -145,10 +145,10 @@ Ingress-based runtimes use ingress controllers to control communication between
145145
{% include
146146
image.html
147147
lightbox="true"
148-
file="/images/getting-started/architecture/arch-hybrid-ingress.png"
149-
url="/images/getting-started/architecture/arch-hybrid-ingress.png"
150-
alt="Ingress-basedhybrid runtime architecture"
151-
caption="Ingress-basedhybrid runtime architecture"
148+
file="/images/runtime/architecture/arch-hybrid-ingress.png"
149+
url="/images/runtime/architecture/arch-hybrid-ingress.png"
150+
alt="Ingress-basedHybrid GitOps runtime architecture"
151+
caption="Ingress-basedHybrid GitOps runtime architecture"
152152
max-width="100%"
153153
%}
154154

-2.34 KB
Loading

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp