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
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ toc: true
7
7
8
8
Codefresh is a Continuous Integration/Delivery (CI/CD) solution. This article reviews main concepts around CD, and how Codefresh supports and implements them.
9
9
10
-
For a review of CI concepts, see[Codefresh for CI]({{site.baseurl}}docs/getting-started/ci-codefresh/).
10
+
For a review of CI concepts, see[Codefresh for CI]({{site.baseurl}}/docs/getting-started/ci-codefresh/).
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 code quality, and generate code-coverage analysis reports.
Copy file name to clipboardExpand all lines: _docs/integrations/git-providers.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
@@ -91,7 +91,7 @@ For more information on generating SSH keys and adding your public key to your V
91
91
##GitHub
92
92
93
93
For the**OAuth2 method** you only need to decide on public/private repository access, enter a name for your connection and click*Save*. Then accept the permissions dialog. This is the easiest and recommended way to integrate GitHub. Notice that if
94
-
you used GitHub when you[created your Codefresh account]({{site.baseurl}}/docs/administration/account-user-management/create-a-codefresh-account/), this integration is already setup for you.
94
+
you used GitHub when you[created your Codefresh account]({{site.baseurl}}/docs/administration/account-user-management/create-codefresh-account/), this integration is already setup for you.
95
95
96
96
For the**Access Token** method you need
97
97
@@ -197,7 +197,7 @@ An alternative way to authenticate with Github is via the App mechanism.
197
197
198
198
For the**OAuth2 method**:
199
199
You only need to enable private repository access, enter a name for your connection and click*Save*. Then accept the permissions dialog. This is the easiest and recommended way to integrate GitLab. Notice that if
200
-
you used GitLab when you[created your Codefresh account]({{site.baseurl}}/docs/administration/account-user-management/create-a-codefresh-account/), this integration is already setup for you.
200
+
you used GitLab when you[created your Codefresh account]({{site.baseurl}}/docs/administration/account-user-management/create-codefresh-account/), this integration is already setup for you.
201
201
202
202
For the**Access Key** method you need:
203
203
@@ -225,7 +225,7 @@ For example if you already have a `token` on a resource call `git-credentials` y
225
225
##Bitbucket
226
226
227
227
For the**OAuth2 method** you only need to enter a name for your connection and click*Save*. Then accept the permissions dialog. This is the easiest and recommended way to integrate Bitbucket. Notice that if
228
-
you used Bitbucket when you[created your Codefresh account]({{site.baseurl}}/docs/administration/account-user-management/create-a-codefresh-account/), this integration is already setup for you.
228
+
you used Bitbucket when you[created your Codefresh account]({{site.baseurl}}/docs/administration/account-user-management/create-codefresh-account/), this integration is already setup for you.
229
229
230
230
For the**Application Password** method you need:
231
231
@@ -302,7 +302,7 @@ caption="Codefresh integration with Azure Devops"
302
302
alt="Codefresh integration with Azure Devops"
303
303
%}
304
304
305
-
Click on*Test connection* to verify your settings and finally click save. Now you can[create pipelines]({{site.baseurl}}/docs/pipeline/pipelines/)
305
+
Click on*Test connection* to verify your settings and finally click save. Now you can[create pipelines]({{site.baseurl}}/docs/pipelines/pipelines/)
###Kubernetes cluster - using an external reverse proxy (edge case)
581
581
582
-
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.
582
+
In case you're using an external reverse proxy to manage inbound traffic to your Kubernetes API, please read[this article]({{site.baseurl}}/docs/troubleshooting/common-issues/verify-cluster-tls-ssl-configuration/) to make sure your certificate setup are managed correctly in order to add your cluster successfully to Codefresh.
Copy file name to clipboardExpand all lines: _docs/terms-and-privacy-policy/terms-of-service.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ text, audio files, graphic files, content, and other materials that you upload,
52
52
53
53
<pstyle='margin-left:1.5rem;'><b>(ix) </b>“<b>Service</b>” means the Site, including related services provided through the site, or the Software.</p>
54
54
55
-
<pstyle='margin-left:1.5rem;'><b>(x) </b>“<b>Site</b>” means Codefresh’s website, located at <ahref="https://support.codefresh.io/">https://support.codefresh.io</a>.</p>
55
+
<pstyle='margin-left:1.5rem;'><b>(x) </b>“<b>Site</b>” means Codefresh’s website, located at <ahref="https://support.codefresh.io/">https://support.codefresh.io</a>.</p>
56
56
57
57
<pstyle='margin-left:1.5rem;'><b>(xi) </b>“<b>SLA</b>” means the “service level agreement” in effect as of the Order’s Effective Date, which can be found at <a
Read this page if you are adding in Codefresh a custom (e.g. on-premises) cluster.
14
+
15
+
##Overview
16
+
17
+
Codefresh connects to your cluster via secure TLS channel, therefore make sure you have configured your cluster and any load balancer or reverse proxy standing in front of it to handle the connection properly.
18
+
19
+
{{site.data.callout.callout_info}}
20
+
#####We need to make sure the following conditions are met:
21
+
22
+
1. The Load Balancer certificate*Common Name corresponds* to the Load Balancer hostname/IP address
23
+
2. When adding the cluster to Codefresh, we provide it with the base64 encoded*CA issuer certificate*, not the Load Balancer server certificate, unless it is a self-signed one
24
+
3. If there is*more than one CA* in the certificate chain, you need to provide the*whole CA bundle file* to Codefresh, not a single CA certificate
25
+
{{site.data.callout.end}}
26
+
27
+
##The exact steps
28
+
29
+
{:start="1"}
30
+
1. Open the URL of your K8 API server, that is the Load Balancer IP (or DNS name) in Chrome using https.
31
+
Let it be, for example:```https://104.198.163.162```
32
+
33
+
{:start="2"}
34
+
2. Open Chrome Developer Tools->Security. Export the server and the CA certificates to file named`loadbalancer_cert` and`ca_cert`. If there is more than one CA, export all of them and combine them into a single bundle file using the following command:
35
+
36
+
{% highlight shell %}
37
+
{% raw %}
38
+
cat intermediateCA.crt rootCA.crt > ca-cert
39
+
{% endraw %}
40
+
{% endhighlight %}
41
+
42
+
{:start="3"}
43
+
3. See the contents of the certificate using the following command:
44
+
45
+
`Shell`
46
+
{% highlight shell %}
47
+
{% raw %}
48
+
openssl x509 -in loadbalancer_cert -text
49
+
{% endraw %}
50
+
{% endhighlight %}
51
+
52
+
53
+
{:start="4"}
54
+
4. See the contents of the CA certificate:
55
+
56
+
`Shell`
57
+
{% highlight shell %}
58
+
{% raw %}
59
+
openssl x509 -in ca_cert -text
60
+
{% endraw %}
61
+
{% endhighlight %}
62
+
63
+
Pay attention to the**flag CA:TRUE** meaning that this is a CA cert. And**Subject: CN** should be the same as in the field**Issuer** of the**Load Balancer certificate**.
64
+
65
+
{:start="5"}
66
+
6.**Verify** that the Load Balancer certificate**is issued by the CA**: