You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/getting-started/cd-codefresh.md
+26-9Lines changed: 26 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,14 +22,13 @@ Dashboards -->
22
22
23
23
24
24
##Connecting to Kubernetes
25
-
Continuous deployment starts with Kubernetes clusters, and 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.
26
-
For those Kubernetes clusters that are not in our list of cluster providers, you can manually enter your cluster settings to add any generic Kubernetes cluster.
25
+
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 Kubernetes clusters is not our list of cluster providers, you can manually enter your cluster settings and add it as a generic Kubernetes cluster.
27
26
28
27
See[Connecting a Kubernetes cluster]({{site.baseurl}}/docs/integrations/kubernetes/#connect-a-kubernetes-cluster).
29
28
30
29
##Deploying to Kubernetes
31
30
Codefresh offers a variety of options for you to choose from when deploying to Kubernetes.
32
-
Deploy to Kubernetes from the Codefresh UI or programmatically through dedicated steps in pipelines, avoiding the need for`kubectl` commands.
31
+
Deploy to Kubernetes from the Codefresh UI, or programmatically through dedicated steps in pipelines avoiding the need for`kubectl` commands.
33
32
34
33
**On-demand deployment**
35
34
For quick and easy deployment, deploy on-demand from the Codefresh UI.
@@ -39,12 +38,12 @@ We have the `deploy` step, and the more advanced `cf-deploy-kubernetes`step that
39
38
40
39
Codefresh pipelines also support Kustomize and Helm for deployments through freestyle steps.
41
40
42
-
Finally, if you are familiar with and want to work with`kubectl`, run your own custom`kubectl` commands in a freestyle step. Read more in[kubectl](#kubectl).
41
+
Finally, if you are familiar with andstillwant to work with`kubectl`, run your own custom`kubectl` commands in a freestyle step. Read more in[kubectl](#kubectl).
43
42
44
43
See[Deployment options for Kubernetes]({{site.baseurl}}/docs/deployments/kubernetes/deployment-options-to-kubernetes/).
45
44
46
45
##kubectl
47
-
`kubectl` is the command line interface for managingkubernetes clusters. Running custom`kubectl` commands in a freestyle step gives maximum flexibility with cluster deployments.
46
+
`kubectl` is the command line interface for managingKubernetes clusters. Running custom`kubectl` commands in a freestyle step gives maximum flexibility with cluster deployments.
48
47
Codefresh automatically sets up your config context with your connected clusters. The config context is the value of the`$CF_KUBECONFIG_PATH` variable, which expands to`/codefresh/volume/sensitive/.kube/config` within the shared step volume.
49
48
50
49
Codefresh has a public Docker image for kubectl at[Docker Hub](https://hub.docker.com/r/codefresh/kubectl/tags){:target="\_blank"} that you can use.
@@ -72,10 +71,25 @@ Deploy Helm charts
72
71
Deploy the Helm chart to a Kubernetes cluster, Helm repo, or both.
73
72
74
73
75
-
##Deployment dashboards
74
+
##Dashboards
75
+
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.
76
76
77
-
TBD
78
-
<!--Dashboards are key to providing the right information at the right time.
77
+
Kubernetes
78
+
79
+
Helm dashboards
80
+
81
+
Helm Releases
82
+
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.
83
+
84
+
Helm promotions
85
+
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).
86
+
87
+
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.
88
+
89
+
**DORA metrics**
90
+
91
+
92
+
<!--
79
93
80
94
Helm Boards
81
95
@@ -90,4 +104,7 @@ Analytical Dashboards ~ Developers often need to reach out to the DevOps team to
90
104
Kubernetes Services
91
105
92
106
Environments
93
-
-->
107
+
-->
108
+
109
+
110
+
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.