Connecting your Kubernetes cluster to the CI/CD platform is the first step in continuous deployment. Codefresh integrates with any known cluster provider for Kubernetes through a few simple steps. Connect your Google, Azure, or Amazon Kubernetes cluster to Codefresh through simple integration steps. If your Kubernetesclusters is not our list of cluster providers, you can manually enter your cluster settings and add it as a generic Kubernetes cluster.

Connecting your Kubernetes cluster to the CI/CD platform is the first step in continuous deployment. Codefresh integrates with any known cluster provider for Kubernetes through a few simple steps. Connect your Google, Azure, or Amazon Kubernetes cluster to Codefresh through simple integration steps. If your Kubernetescluster is not in our list of cluster providers, you can manually enter your cluster settings and add it as a generic Kubernetes cluster.

See[Connecting a Kubernetes cluster]({{site.baseurl}}/docs/integrations/kubernetes/#connect-a-kubernetes-cluster).

Deploy to Kubernetes from the Codefresh UI, or programmatically through dedicated steps in pipelines avoiding the need for`kubectl` commands.

**On-demand deployment**

For quick and easy deployment, deploy on-demand from the Codefresh UI.

For quick and easy deployment,you candeploy on-demand from the Codefresh UI.

**Dedicated steps in pipelines**

Wehave the`deploy` step, and the more advanced`cf-deploy-kubernetes`stepthat enables simple templating on Kubernetes manifests.

For more flexibility, wehavededicated steps for pipelines,the`deploy` step, and the more advanced`cf-deploy-kubernetes`stepwhich enables simple templating on Kubernetes manifests.

Codefresh pipelines also support Kustomize and Helm for deployments through freestyle steps.

See[Running custom kubectl commands]({{site.baseurl}}/docs/deployments/kubernetes/custom-kubectl-commands/).

Codefresh supplies a built-in Helm repository with every Codefresh account. And supports, besides public HTTP repositories, several private, authenticated Helm repositories.

**Connect to Helm repositories**

In addition to the official Helm repositories which are displayed in the Helm charts, Codefresh allows you connect with any external Helm repository through simple integrations. You can then inject the Helm repository context into your pipelines by selecting the repository name.

In addition to the official Helm repositories which are displayed in the Helm charts, Codefresh allows youtoconnect with any external Helm repository through simple integrations. You can then inject the Helm repository context into your pipelines by selecting the repository name.

**Build Helm charts**

Install Helm charts from Helm repositories, or build a new one.

Install Helm charts from Helm repositories, or build a new one.

As with steps for Kubernetes deployments, Codefresh has a dedicated step for Helm deployments. The Helm step easily integrates Helm in Codefresh pipelines, and can authenticate, configure, and execute Helm commands.

The Helm step can operate in one of three modes covering most scenarios:

* Install the chart into a Kubernetes cluster. This is the default mode if not explicitly set.

* Package the chart and push it to the defined repository.

* Setup authentication and add the repo to Helm. This is useful if you want to write your ownHelm commands using the freestyle step’s commands property, but you still want the step to handle authentication.

Deploy Helm charts

**Deploy Helm charts**

Deploy the Helm chart to a Kubernetes cluster, Helm repo, or both.

See[Using Helm in Codefresh pipelines]({{site.baseurl}}/docs/deployments/helm//using-helm-in-codefresh-pipeline/),[Using managed Helm repos]({{site.baseurl}}/docs/deployments/helm//managed-helm-repository/), and Helm[charts and repositories]({{site.baseurl}}/docs/deployments/helm/helm-charts-and-repositories/).

Dashboards are key to providing the right information at the right time. Codefresh makes it easy to both access and visualize critical information for any CI/CD resource at any stage, at any level, and for anyone, from managers to DevOps engineers.

Kubernetes

Dashboards are key to providing the right information at the right time. Codefresh makes it easy to both access and visualize critical information for any resource at any stage, at any level, and for anyone, from managers to DevOps engineers. Our operational dashboards expose the most critical application and environmental information to developers for troubleshooting without needing assistance from the DevOps teams. Our analytics dashboards expose key statistics and metrics around builds and deployments for product owners and management alike.

Helm dashboards

Helm Releases

The Helm Releases dashboard provides a unique view into your production Kubernetes cluster, and actions for deployed releases. See the current status of your cluster, including the currently deployed releases, their previous revisions with change tracking, and even roll back to a previous release.

You can customize all dashboards to display just the information most relevant to your business issues.

Helm promotions

Codefresh also comes with a special environment board that allows you to track one or more applications as they move within your infrastructure (e.g., Dev, QA, Prod).

**Kubernetes**

The Kubernetes (Kubernetes Services) dashboard displays the clusters in your environments, their state, and actions if you have the required access privileges.

The dashboard is a centralized location from which to view, add, modify, and remove Kubernetes services. You can deploy services with images from the Codefresh registry or from external Docker registries.

See[Accessing the Kubernetes dashboard]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/#accessing-the-kubernetes-dashboard).

The environment board can function both as an overview of the whole lifecycle of the application as well as a tool to shift-left/right Helm releases between environments.

**Helm dashboards**

For Helm we have a Helm Board, and a Helm Releases dashboard.

**DORA metrics**

* Helm Boards

The Helm Board is a special environment board that allows you to track one or more applications as they move within your infrastructure. For example, between Dev, QA and Prod environments.

Here you can see the lifecycle of the application, and at the same time, use it as a tool shift Helm releases between environments.

You can create as many Helm Boards as you want, and customize the Helm Boards with the columns to display, each column being a Helm-enabled Kubernetes cluster.

See[Using the Helm Board]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion/#using-the-helm-environment-board).

* Helm Releases

The Helm Releases dashboard provides a unique view into your production Kubernetes cluster, and options to manage deployed releases. See the current status of your cluster, including the currently deployed releases, their previous revisions with change tracking. If needed, you can even roll back to a previous release.

See[View Helm releases and release information]({{site.baseurl}}/docs/deployments/helm/helm-releases-management/#view-helm-releases-and-release-information).

**Environment dashboard**

The Kubernetes dashboard shows cluster status and focuses more on the service aspects such as pods and Docker images. The Helm Board offers an application-level view of your cluster, as it applies to Helm deployments.

To bridge this gap, Codefresh also offers an Environment dashboard that combinesinformationfor both Kubernetes and Helm releases. Youcansee cluster status in the context ofthepipeline builds that run on and affect the cluster. It links between the status of the cluster and the status of the builds.

**DORA metrics**

The DORA (DevOps Research and Assessment) metrics dashboard pulls out critical metrics for our GitOps deployments. The metrics include deployment frequency, lead time for changes, mean time to recovery, and change failure rate. The metric graphs show performance by default for the last 90 days, with the option to select daily/weekly/monthly granularity views.

See[DORA metrics]({{site.baseurl}}/docs/dashboards/dora-metrics/).

Second, we’re announcing The Universal Dashboard with DORA metrics. User’s of Codefresh’s GitOps Control Plane have enjoyed being able to navigate across many instances of GitOps runtimes (an enterprise version of Argo CD/Rollouts). We’re greatly amplifying those capabilities with the Universal Dashboard by automatically pulling out critical metrics. The holy grail of DevOps metrics are DORA (DevOps Research and Assessment) which include deployment frequency, lead time for changes, mean time to recovery, and change failure rate.

[Codefresh for CI]({{site.baseurl}}/docs/getting-started/ci-codefresh/)

[Concepts in Codefresh]({{site.baseurl}}/docs/getting-started/concepts/)

Codefresh supports all testing frameworks, including mocking frameworks, for all popular programming languages. Easily run unit tests on the source code of the application for every commit or pull request (PR) through our freestyle step in pipelines.

Run any type of unit tests in Codefresh pipelines, from smoke tests in a dockerfile, to tests with external or application images for simple applications, andevenrun them on a special testing image for complex applications.

Run any type of unit tests in Codefresh pipelines, from smoke tests in a dockerfile, to tests with external or application images for simple applications, andeven run them on a special testing image for complex applications.

You can create test reports and view them whenever you need.

See:

[Run integration tests example]({{site.baseurl}}/docs/example-catalog/ci-examples/run-integrations-tests/)

Good quality code is central to any CI platform or tool. Codefresh integrates with the top code quality platforms/tools in the market to track code coverage, inspect codequailty, and generate code-coverage analysis reports.

Good quality code is central to any CI platform or tool. Codefresh integrates with the top code quality platforms/tools in the market to track code coverage, inspect codequality, and generate code-coverage analysis reports.

Implement code quality coverage in Codefresh pipelines through these steps:

* Set up integrations with the platforms/tools (Coverall, SonarQube, Codecov, for example).

Linting and validation tools which perform static analysis on source code or other resources are also integralpart of pipelines. Codefresh pipelines can use any linter tool that is bundled with a Docker image. Codefresh can also validate files that are not source-code, such as markup-language files (XML/YAML/JSON), infrastructure files (Terraform, or Kubernetes resource files).

Linting and validation tools which perform static analysis on source code or other resources are also integralparts of pipelines. Codefresh pipelines can use any linter tool that is bundled with a Docker image. Codefresh can also validate files that are not source-code, such as markup-language files (XML/YAML/JSON), infrastructure files (Terraform, or Kubernetes resource files).

Most static analysis tools are CLI-based, and can be easily used in a Codefresh pipeline.

As with any scan, the final step is viewing the scan results. Make the scan results available in Codefresh release dashboards (Test Report button) by attaching analysis reports to the pipeline build.

**Security annotations**

Correlate the Docker images in Codefresh with the results of the security scanning platform by adding annotations for custommetatdata. For example, you can add annotations such as the number of issues or the URL of the full report.

Correlate the Docker images in Codefresh with the results of the security scanning platform by adding annotations for custommetadata. For example, you can add annotations such as the number of issues or the URL of the full report.

See:

[Security scanning tests]({{site.baseurl}}/docs/testing/security-scanning/)

See[Jira notifications in Codefresh]({{site.baseurl}}/docs/integrations/notifications/jira-integration/) and[examples for Jira notification]({{site.baseurl}}/docs/example-catalog/ci-examples/sending-the-notification-to-jira/).

[Codefresh for CD]({{site.baseurl}}/docs/getting-started/cd-codefresh/)

[Codefresh for CD]({{site.baseurl}}/docs/getting-started/cd-codefresh/)

[Concepts in Codefresh]({{site.baseurl}}/docs/getting-started/concepts/)

The Runner is the hybrid installation option forCI/CDpipelines in your Codefresh account. The Runner is installed as a Kubernetes native application on any Kubernetes-compliant cluster. It allows you to run pipelines on your own Kubernetes cluster, including private clusters behind company firewalls.

The Runner is the hybrid installation option for pipelines in your Codefresh account. The Runner is installed as a Kubernetes native application on any Kubernetes-compliant cluster. It allows you to run pipelines on your own Kubernetes cluster, including private clusters behind company firewalls.

Codefresh Runner gives you:

* Access to secure services (such as Git repositories or databases) that are behind the firewall and normally not accessible to the public cloud.

A project is a top-level entity in Codefresh for grouping related pipelines. Projects can group pipelines according to any criteria that is relevant to your enterprise. The criteria can be logical and based on teams, departments, or location for example, or funtional, and based microservices in applications.

A project is a top-level entity in Codefresh for grouping related pipelines. Projects can group pipelines according to any criteria that is relevant to your enterprise. The criteria can be logical and based on teams, departments, or location for example, or funtional, and basedonmicroservices in applications.

Projects centralize viewing and configuration settings for the pipelines that belong to them:

* Selecting a pipeline shows the other pipelines in the same project.

*Define accesscontrol and user-defined variables for the project, and they are inherited by all the pipelines assigned to the project

* Selecting a pipeline shows the other pipelines in the same project

*Accesscontrol and user-defined variables for the project are inherited by all the pipelines assigned to the project

There are no limits to the number of projects you can create in your account. You can also create standalone pipelines and assign them later to a project, or detach a pipeline assigned to a project.

TBW

An application is a deployment to a Kubernetes, or any Kubernetes-compatiale cluster or clusters.

An application is a deployment to a Kubernetes, or any Kubernetes-compatible cluster or clusters.

Codefresh supports two types of applications:

* Containerized applications packaged as Docker images or

* Argo CD applications

TBD

Triggers are events that launch pipelines and Argo Workflows in Codefresh.

A trigger can define an event defines an event or events, mapped to one or more Git repositories.

Codefresh offers a rich set of triggers

and defines an event or event or events defined in pipelines and Argo Workflows that are mapped to one or more Git Codefresh offers a rich set of triggers that you can select and define through the Codefresh UI as part of creating an Argo Workflow. These include Git and Cron triggers. The triggers and the event that are mapped to sensors and

TBD

[Codefresh for CI]({{site.baseurl}}/docs/getting-started/ci-codefresh/)

[Codefresh for CD]({{site.baseurl}}/docs/getting-started/cd-codefresh/)