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/integrations/codefresh-hosted-gitops.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,16 +5,16 @@ group: integrations
5
5
toc:true
6
6
---
7
7
8
-
Integrate CodefreshClassic with Codefresh's Hosted GitOps for deployments powered by managed Argo CD.
8
+
Integrate CodefreshCI with Hosted GitOps for deployments powered by managed Argo CD.
9
9
Use Codefresh Classic for pipelines, and Codefresh Hosted GitOps for deployments.
10
10
11
-
Codefresh Hosted GitOps includes a dedicated report image step that both reports and enriches deployed images. Add the report image step in your CodefreshClassic pipeline and reference integrations with issue-tracking and container registry tools for Codefresh to retrieve and enrich image information.
11
+
Codefresh Hosted GitOps includes a dedicated report image step that both reports and enriches deployed images. Add the report image step in your CodefreshCI pipeline and reference integrations with issue-tracking and container registry tools for Codefresh to retrieve and enrich image information.
12
12
13
13
For a brief overview of what you get with Codefresh Hosted GitOps, read the next section.
14
14
15
-
For information on how to connectCodefresh ClassictoCodefreshHosted GitOps, see[CI integration with Codefresh Classic](https://codefresh.io/docs/gitops-integrations/ci-integrations/codefresh-classic/){:target="\_blank"}.
15
+
For information on how to connect to Hosted GitOps, see[CI integration with Codefresh Classic]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/codefresh-classic/).
16
16
17
-
##CodefreshHosted GitOps features
17
+
##Hosted GitOps features
18
18
19
19
###Hosted and hybrid runtimes
20
20
Codefresh Hosted GitOps is based on a hosted environemt, with the runtime hosted and managed by Codefresh.
Copy file name to clipboardExpand all lines: _docs/integrations/kubernetes.md
+36-38Lines changed: 36 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,9 @@ Codefresh has native support for Kubernetes in the following areas:
11
11
12
12
-[Connecting a cluster globally](#connect-a-kubernetes-cluster)
13
13
-[Viewing the cluster status]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/)
14
-
-[Viewing the environment dashboard]({{site.baseurl}}/docs/deployments/kubernetes/environment-dashboard/)
15
-
-[Deploying to a cluster with the GUI]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/#deploying-a-new-service)
16
-
-[Deploying to a cluster with a pipeline]({{site.baseurl}}/docs/deployments/kubernetes/deployment-options-to-kubernetes/)
14
+
-[Viewing the environment dashboard](/#viewing-the-environment-dashboard)
15
+
-[Deploying to a cluster with the GUI](#ad-hoc-deployments-with-the-codefresh-ui)
16
+
-[Deploying to a cluster with a pipeline](#automated-deployments-with-codefresh-pipelines)
17
17
-[Running pipelines on a cluster]({{site.baseurl}}/docs/installation/codefresh-runner/)
18
18
19
19
@@ -27,10 +27,10 @@ in your cluster. To activate this dashboard, you need to connect your cluster to
27
27
###Prerequisites
28
28
29
29
Codefresh SaaS needs network connectivity to connect to your cluster.
30
-
If your cluster is behind a firewall, make sure that you allow access to the[required IPs]({{site.baseurl}}/docs/administration/platform-ip-addresses/).
30
+
If your cluster is behind a firewall, make sure that you allow access to the[required IPs]({{site.baseurl}}/docs/administration/account-user-management/platform-ip-addresses/).
31
31
32
32
33
-
ForOn-premises and[Hybrid installations]({{site.baseurl}}/docs/administration/behind-the-firewall/), there is no need totamper with your firewall.
33
+
Foron-premises and[hybrid installations with Runner]({{site.baseurl}}/docs/installation/behind-the-firewall/), there is no need totweak your firewall.
34
34
35
35
###Set up Kubernetes integration
36
36
@@ -49,24 +49,21 @@ For On-premises and [Hybrid installations]({{site.baseurl}}/docs/administration/
49
49
50
50
51
51
52
-
####Adding a GKE Cluster
52
+
###Adding a GKE Cluster
53
53
Adding a cluster in GKE can be done by clicking the**Add cluster** button under**Google Cloud Provider** and selecting the desired project and cluster.
54
54
55
55
If this is your first time, you'll be prompted to authenticate using your Google credentials, make sure you're doing so with a user that have access to your GKE projects.
56
56
57
-
For GKE cluster versions >=1.19 basic authentication is deprecated. You can add the GKE cluster manually by[using the custom Kubernetes integration option]({{site.baseurl}}/docs/deploy-to-kubernetes/add-kubernetes-cluster/#adding-any-other-cluster-type-not-dependent-on-any-provider) instead.
57
+
For GKE cluster versions >=1.19 basic authentication is deprecated. You can add the GKE cluster manually by[using the custom Kubernetes integration option](#adding-any-other-cluster-type-not-dependent-on-any-provider) instead.
58
58
59
59
{{site.data.callout.callout_info}}
60
60
61
61
If you are a new customer of Google Cloud, you are also eligible to receive a Codefresh offer to get up to $500 in Google credits. As soon at the GKE integration is complete within Codefresh, you will get an email with extra details on how to claim your credits.
62
62
63
63
Follow the link in the email to fill in an application for the free credits. Once Google approves the application (usually within 1-2 days) your credits will be available to your account. Make sure to check your spam folder for that email.
64
64
65
-
{{site.data.callout.end}}
66
65
67
-
{:.text-secondary}
68
-
69
-
####Adding an AKS cluster
66
+
###Adding an AKS cluster
70
67
71
68
To add an Azure cluster, select*Azure AKS* from the drop-down menu instead of*Azure AKS SP*. Click the*Authenticate button* and enter your Azure credentials. You will see a description of all permissions that Codefresh needs
72
69
in order to access your cluster. Accept them and Codefresh will connect to Azure to get the cluster information.
@@ -86,9 +83,9 @@ caption="Selecting the Azure cluster"
86
83
max-width="60%"
87
84
%}
88
85
89
-
Codefresh will query the cluster and show its nodes. You are now ready to[deploy to Azure kubernetes]({{site.baseurl}}/docs/getting-started/deployment-to-kubernetes-quick-start-guide/).
86
+
Codefresh will query the cluster and show its nodes. You are now ready to[deploy to Azure kubernetes]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-to-kubernetes/).
90
87
91
-
>If you wish for any reason to revoke the granted access from the Azure side, visit[https://account.activedirectory.windowsazure.com/r#/applications](https://account.activedirectory.windowsazure.com/r#/applications) and remove "Codefresh" from the list.
88
+
>If you wish for any reason to revoke the granted access from the Azure side, visit[https://account.activedirectory.windowsazure.com/r#/applications](https://account.activedirectory.windowsazure.com/r#/applications){:target="\_blank"} and remove "Codefresh" from the list.
92
89
93
90
####Adding an AKS cluster with a service principal
94
91
@@ -111,19 +108,20 @@ An alternative method of adding an Azure cluster is by using a service principal
Codefresh will query the cluster and show its nodes. You are now ready to[deploy to Azure kubernetes]({{site.baseurl}}/docs/getting-started/deployment-to-kubernetes-quick-start-guide/).
120
+
Codefresh will query the cluster and show its nodes. You are now ready to deploy to Azure kubernetes.
121
+
124
122
125
123
126
-
####Adding EKS Cluster
124
+
###Adding EKS Cluster
127
125
128
126
To add an Amazon EKS cluster, you must first obtain`kubectl` access to it. Follow the instructions for using the
129
127
[AWS CLI](https://aws.amazon.com/premiumsupport/knowledge-center/eks-cluster-connection/){:target="\_blank"} in order to obtain your kubeconfig locally.
@@ -132,19 +130,19 @@ To add an Amazon EKS cluster, you must first obtain `kubectl` access to it. Foll
132
130
aws eks --region region update-kubeconfig --name cluster_name
133
131
```
134
132
135
-
Once you have access via`kubectl` then follow the[instructions](#get-cluster-configuration-manually) to obtain all the cluster details.
133
+
Once you have access via`kubectl`, then follow the[instructions](#get-cluster-configuration-manually) to obtain all the cluster details.
136
134
To add the Amazon cluster, select*Amazon AWS* from the*ADD PROVIDER* drop-down menu and enter all details in the respective field in the Codefresh UI.
137
135
138
-
####Adding a DigitalOcean cluster
136
+
###Adding a DigitalOcean cluster
139
137
140
138
DigitalOcean also offers a hosted solution for Kubernetes.
141
139
142
-
To add a DO cluster select*DigitalOcean* from the*Add provider* menu in your[integration settings](https://g.codefresh.io/account-admin/account-conf/integration/kubernetes). Click the authenticate button and enter your DO account credentials:
140
+
To add a DO cluster select*DigitalOcean* from the*Add provider* menu in your[integration settings](https://g.codefresh.io/account-admin/account-conf/integration/kubernetes){:target="\_blank"}. Click the authenticate button and enter your DO account credentials:
Your cluster is now connected. You should be able to see it your[Kubernetes dashboard]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/) and start[deploying]({{site.baseurl}}/docs/getting-started/deployment-to-kubernetes-quick-start-guide/)on it.
173
+
Your cluster is now connected. You should be able to see it your[Kubernetes dashboard]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/), and start[deploying]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-to-kubernetes/)to it.
176
174
177
-
Note that you canals add a DigitalOcean cluster as a generic cluster as well (explained below).
175
+
Note that you canalso add a DigitalOcean cluster as a generic cluster as well (explained below).
178
176
179
177
180
-
####Adding any other cluster type (not dependent on any provider)
178
+
###Adding any other cluster type (not dependent on any provider)
181
179
182
180
183
181
@@ -215,7 +213,7 @@ The configurations you'll be required to add are:
215
213
max-width="80%"
216
214
%}
217
215
218
-
There is also a toggle for[private clusters behind a firewall]({{site.baseurl}}/docs/reference/behind-the-firewall/).
216
+
There is also a toggle for[private clusters behind a firewall]({{site.baseurl}}/docs/installation/behind-the-firewall/).
219
217
220
218
In the section below, we'll provide you with easy instructions how to get all your cluster configurations in order to add it to Codefresh.
221
219
@@ -505,7 +503,7 @@ Notice that if you follow this approach several built-in Codefresh capabilities
505
503
506
504
###Adding a Rancher cluster
507
505
508
-
Rancher clusters are currently supported as generic clusters. Rancher clusters have a specific authentication configuration (the details are here:[https://rancher.com/kubernetes-authentication-in-rancher-and-rbac](https://rancher.com/kubernetes-authentication-in-rancher-and-rbac){:target="\_blank"} forRancher1.x and at[https://rancher.com/blog/2018/2018-05-04-authentication-authorization-rancher2/](https://rancher.com/blog/2018/2018-05-04-authentication-authorization-rancher2/){:target="\_blank"} for Rancher 2.x).
506
+
Rancher clusters are currently supported as generic clusters. Rancher clusters have a specific authentication configuration, as described for[Rancher 1.x](https://rancher.com/kubernetes-authentication-in-rancher-and-rbac){:target="\_blank"}, and[Rancher2.x](https://rancher.com/blog/2018/2018-05-04-authentication-authorization-rancher2/){:target="\_blank"}.
509
507
510
508
Authentication using a token of a Kubernetes Service Account, which is usually used by Codefresh, doesn't work with Rancher clusters. Also, Rancher doesn't do proper TLS termination out-of-the-box for Kubernetes clusters hosted on it, so one needs to configure a load balancer for that purpose.
511
509
@@ -559,7 +557,7 @@ After adding your cluster configurations and in case the test fails, click "Save
###Kubernetes cluster - using an external reverse proxy (edge case)
584
582
585
-
In case you're using an external reverse proxy to manage inbound traffic to your Kubernetes API, please read[this article]({{site.baseurl}}/docs/deploy-to-kubernetes/verify-cluster-tls-ssl-configuration/) to make sure your certificate setup are managed correctly in order to add your cluster successfully to Codefresh.
583
+
In case you're using an external reverse proxy to manage inbound traffic to your Kubernetes API, please read[this article]({{site.baseurl}}/docs/deployments/kubernetes/verify-cluster-tls-ssl-configuration/) to make sure your certificate setup are managed correctly in order to add your cluster successfully to Codefresh.
586
584
587
585
###Multiple CAs in certificate chain
588
586
589
587
Ideally your Kubernetes cluster will have a single certificate which is used directly on the API endpoint. Some organizations
590
588
place clusters behind a load balancer or other proxy mechanism that uses a chain or certificates.
591
589
592
-
When that happens and you more than one[CA](https://en.wikipedia.org/wiki/Certificate_authority) in your certification chain, you need to provide Codefresh with a[Certificate bundle](https://en.wikipedia.org/wiki/Chain_of_trust) (a file that containers the intermediate CAs as well).
590
+
When that happens and youhavemore than one[CA](https://en.wikipedia.org/wiki/Certificate_authority){:target="\_blank"} in your certification chain, you need to provide Codefresh with a[Certificate bundle](https://en.wikipedia.org/wiki/Chain_of_trust){:target="\_blank"} (a file that containers the intermediate CAs as well).
593
591
594
592
You will know when this is the case as this error will appear when you try to connect your cluster:
595
593
@@ -601,8 +599,8 @@ To get the whole certificate open the URL of your Kubernetes in Chrome or Firefo
Once you connect a cluster it gets a unique name inside your account that is important when it comes to using this cluster inside a pipeline. From the same screen you can also connect[internal clusters that are behind your firewall]({{site.baseurl}}/docs/reference/behind-the-firewall/#deploying-to-an-internal-kubernetes-cluster/).
644
+
Once you connect a cluster it gets a unique name inside your account that is important when it comes to using this cluster inside a pipeline. From the same screen you can also connect[internal clusters that are behind your firewall]({{site.baseurl}}/docs/installation/behind-the-firewall/#deploying-to-an-internal-kubernetes-cluster/).
647
645
.
648
646
649
647
##Viewing the Codefresh cluster dashboard
650
648
651
-
After you connect a cluster, several graphical dashboards are automatically populated. The first one is the[Codefresh Kubernetes dashboard]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/).
649
+
After you connect a cluster, several graphical dashboards are automatically populated. The first one is the[Codefresh Kubernetes dashboard]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/#accessing-the-kubernetes-dashboard).