Skip to content

Updates #279

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Updates #279

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 2 additions & 6 deletions _data/home-content.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,4 @@





- title: Pipelines
icon: images/home-icons/pipeline.svg
url: ''
Expand Down Expand Up @@ -59,9 +55,9 @@
links:
- title: Installation environments
localurl: /docs/installation/installation-options/
- title: Codefresh Runner CI/CD installation
- title: Runner installation
localurl: /docs/installation/codefresh-runner/
- title: On-Premises CI/CD installation
- title: On-Premises installation
localurl: /docs/installation/codefresh-on-prem/
- title: On-Premises CI/CD upgrade
localurl: /docs/installation/codefresh-on-prem-upgrade/
Expand Down
30 changes: 16 additions & 14 deletions _docs/installation/installation-options.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,13 @@ description: ""
group: installation
toc: true
---
To be changed and updated for ProjectOne
TBD

The Codefresh platform supports two different installation environments, each with different installation options.
The Codefresh platform supports two environments, each with different installation options.

* CI/CD installation environment
<!--

CI/CD installation environment
The CI/CD installation environment is optimized for Continuous Integration/Delivery with Codefresh pipelines. CI pipelines created in Codefresh fetch code from your Git repository, packages/compiles the code, and deploys the final artifact to a target environment.

The CI/CD installation environment supports these installation options:
Expand All @@ -21,15 +23,14 @@ The Codefresh platform supports two different installation environments, each wi
* GitOps installation environment
The GitOps installation environment is a full-featured solution for application deployments and releases. Powered by the Argo Project, Codefresh uses Argo CD, Argo Workflows, Argo Events, and Argo Rollouts, extended with unique functionality and features essential for enterprise deployments.

GitOps installations support Hosted and Hybrid options.
GitOps installations support Hosted and Hybrid options. -->

## Comparison
Both environments can co-exist giving you the best of both worlds. For

TBD


## Codefresh CI/CD installation options



Expand All @@ -39,9 +40,10 @@ TBD



### Codefresh Cloud CI/CD - likely to be removed

The Codefresh CI/CD Cloud version is the easiest way to start using Codefresh as it is fully managed and runs 100% on the cloud. Codefresh DevOps handles the maintenance and updates.
## Codefresh SaaS - likely to be removed

The Codefresh Cloud version is the easiest way to start using Codefresh as it is fully managed and runs 100% on the cloud. Codefresh DevOps handles the maintenance and updates.

You can also create a [free account]({{site.baseurl}}/docs/getting-started/create-a-codefresh-account/) on the SAAS version right away. The account is forever free with some limitations
on number of builds.
Expand Down Expand Up @@ -69,9 +71,9 @@ Codefresh Cloud is also compliant with [SOC2 - Type2](https://www.aicpa.org/SOC)
The Cloud version has multi-account support with most git providers (GitLab, GitHub, Bitbucket) as well as Azure and Google.


### Codefresh Hybrid CI/CD
## Codefresh Runner

The Hybrid CI/CD installation option is for organizations who want their source code to live within their premises, or have other security constraints. For more about the theory and implementation, see [CI/CD behind the firewall installation]({{site.baseurl}}/docs/administration/behind-the-firewall/).
The Codefresh Runner installation option is for organizations who want their source code to live within their premises, or have other security constraints. For more about the theory and implementation, see [CI/CD behind the firewall installation]({{site.baseurl}}/docs/administration/behind-the-firewall/).

The UI runs on Codefresh infrastructure, while the builds happen in a Kubernetes cluster in the customer's premises.

Expand All @@ -84,13 +86,13 @@ The UI runs on Codefresh infrastructure, while the builds happen in a Kubernetes
%}


CI/CD Hybrid installation strikes the perfect balance between security, flexibility, and ease of use. Codefresh still does the heavy lifting for maintaining most of the platform parts. The sensitive data (such as source code and internal services) never leave the premises of the customers.
Hybrid installation strikes the perfect balance between security, flexibility, and ease of use. Codefresh still does the heavy lifting for maintaining most of the platform parts. The sensitive data (such as source code and internal services) never leave the premises of the customers.

With Hybrid CI/CD installation, Codefresh can easily connect to internal [secure services]({{site.baseurl}}/docs/reference/behind-the-firewall/#using-secure-services-in-your-pipelines) that have no public presence.
The UI part is still compliant with Soc2.


Here are the security implications of CI/CD Hybrid installation:
Here are the security implications of Hybrid installation:

{: .table .table-bordered .table-hover}
| Company Asset | Flow/Storage of data | Comments |
Expand Down Expand Up @@ -122,13 +124,13 @@ Here are the security implications of CI/CD Hybrid installation:



### Codefresh On-premises CI/CD
## Codefresh On-premises

For customers who want full control, Codefresh also offers an on-premises option for CI/CD installation. Both the UI and builds run on a Kubernetes cluster fully managed by the customer.

While Codefresh can still help with maintenance of the CI/CD On-premises, we would recommend the Hybrid CI/CD option first as it offers the most flexibility while maintaining high security.

### CI/CD installation comparison
## Installation comparison

{: .table .table-bordered .table-hover}
| Characteristic | Cloud | Hybrid | On Premise |
Expand All @@ -144,7 +146,7 @@ While Codefresh can still help with maintenance of the CI/CD On-premises, we wou

## Codefresh GitOps installation options

Similar to CI/CD installation options, Codefresh GitOps also supports SaaS and hybrid installation options:
Codefresh GitOps also supports hosted and hybrid installation options:


### Hosted GitOps
Expand Down
10 changes: 5 additions & 5 deletions _docs/installation/runtime-architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ toc: true

Overview TBD

## Codefresh CI/CD architecture
## Codefresh Runner architecture

The most important components are the following:

Expand All @@ -17,7 +17,7 @@ The most important components are the following:

**External actors**. Codefresh offers a [public API]({{site.baseurl}}/docs/integrations/ci-integrations/codefresh-api/) that is consumed both by the Web user interface and the <!--should i differentiate between the CI Cli and GitOps CLI -->[Codefresh CLI](https://codefresh-io.github.io/cli/){:target="\_blank"}. The API is also available for any custom integration with external tools or services.

### CI/CD topology
### Runner topology

If we zoom into Codefresh Services for CI/CD, we will see the following:

Expand All @@ -30,7 +30,7 @@ If we zoom into Codefresh Services for CI/CD, we will see the following:
max-width="100%"
%}

### CI/CD core components
### Runner core components

{: .table .table-bordered .table-hover}
|Category | Component | Function |
Expand All @@ -52,9 +52,9 @@ If we zoom into Codefresh Services for CI/CD, we will see the following:
| | **tasker-kubernetes** | Provides cache storage for Kubernetes dashboards. See [Kubernetes dashboards]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/). |


## Codefresh GitOps Platform architecture
## Codefresh GitOps architecture

The diagram shows a high-level view of the Codefresh GitOps installation environment, and its core components, the Codefresh Control Plane, the Codefresh Runtime, and the Codefresh Clients.
The diagram shows a high-level view of the Codefresh GitOps installation environment, and its core components, the Codefresh Control Plane, the Codefresh GitOps Runtime, and the Codefresh Clients.

{% include
image.html
Expand Down