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/codefresh-yaml/advanced-workflows.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -804,7 +804,7 @@ In this case Codefresh will make sure that cleanup happens only when both unit a
804
804
805
805
For maximum flexibility you can define a custom conditional for a step.
806
806
807
-
It is hard to describe all possible cases, because Codefresh support a[mini DSL]({{site.baseurl}}/docs/codefresh-yaml/expression-condition-syntax/) for conditions. All examples mentioned in[conditional execution]({{site.baseurl}}/docs/codefresh-yaml/conditional-execution-of-steps/) are still valid in parallel pipelines.
807
+
It is hard to describe all possible cases, because Codefresh support a[mini DSL]({{site.baseurl}}/docs/codefresh-yaml/condition-expression-syntax/) for conditions. All examples mentioned in[conditional execution]({{site.baseurl}}/docs/codefresh-yaml/conditional-execution-of-steps/) are still valid in parallel pipelines.
808
808
809
809
For example, run this step only if a PR is opened against the production branch:
810
810
@@ -962,7 +962,7 @@ Notice that both examples assume that `fail_fast: false` is at the root of the `
Copy file name to clipboardExpand all lines: _docs/codefresh-yaml/annotations.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
@@ -159,7 +159,7 @@ Click *Save* to apply your changes.
159
159
160
160
##Complex annotation values
161
161
162
-
Apart from scalar values, you can also store more complex expressions in annotations. You have access to all[Codefresh variables]({{site.baseurl}}/docs/codefresh-yaml/variables/), text files from the build and even evaluations from the[expression syntax]({{site.baseurl}}/docs/codefresh-yaml/expression-condition-syntax/)
162
+
Apart from scalar values, you can also store more complex expressions in annotations. You have access to all[Codefresh variables]({{site.baseurl}}/docs/codefresh-yaml/variables/), text files from the build and even evaluations from the[expression syntax]({{site.baseurl}}/docs/codefresh-yaml/condition-expression-syntax/)
Each step in`codefresh.yml` file can containexpressionconditions that must be satisfied for the step to execute.
10
+
Each step in`codefresh.yml` file can contain conditions expressions that must be satisfied for the step to execute.
10
11
11
-
This is a small example of whereanexpressioncondition can be used:
12
+
This is a small example of wherea conditionexpression can be used:
12
13
`YAML`
13
14
{% highlight yaml %}
14
15
step-name:
@@ -23,7 +24,7 @@ step-name:
23
24
executeForMasterBranch: "{% raw %}'${{CF_BRANCH}}{% endraw %}' == 'master'"
24
25
{% endhighlight %}
25
26
26
-
Aexpressioncondition is a basic expression that is evaluated to true/false (to decide whether to execute or not to execute), and can have the following syntax:
27
+
A condition expression is a basic expression that is evaluated to true/false (to decide whether to execute or not to execute), and can have the following syntax:
Copy file name to clipboardExpand all lines: _docs/codefresh-yaml/conditional-execution-of-steps.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,10 +65,10 @@ build-step:
65
65
The[JavaScript regular expressions](https://developer.mozilla.org/en/docs/Web/JavaScript/Guide/Regular_Expressions) flavour is the one used in branch conditions.
66
66
{{site.data.callout.end}}
67
67
68
-
##Expression Conditions
69
-
Alternatively, you can use more advancedexpression conditions.
68
+
##Condition expressions
69
+
Alternatively, you can use more advancedcondition expressions.
70
70
71
-
This follows the standard[expressioncondition syntax]({{site.baseurl}}/docs/codefresh-yaml/expression-condition-syntax/). In this case, you can choose to execute if```all``` expression conditions evaluate to```true```, or to execute if```any``` expression conditions evaluate to```true```.
71
+
This follows the standard[conditionexpression syntax]({{site.baseurl}}/docs/codefresh-yaml/condition-expression-syntax/). In this case, you can choose to execute if```all``` expression conditions evaluate to```true```, or to execute if```any``` expression conditions evaluate to```true```.
72
72
73
73
Here are some examples. Execute if the string```[skip ci]``` is not part of the main repository commit message AND if the branch is```master```
Copy file name to clipboardExpand all lines: _docs/deploy-to-kubernetes/add-kubernetes-cluster.md
+4-10Lines changed: 4 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -244,17 +244,11 @@ The integration between Codefresh and your Kubernetes cluster is API based and r
244
244
245
245
The configurations you'll be required to add are:
246
246
247
-
{:start="1"}
248
-
1. Name - Any name of your choosing, that will represent your cluster context in Codefresh. Do not use spaces, dots or other strange characters in the name.
249
-
250
-
{:start="2"}
251
-
2. Host - The full URL of the Kubernetes API endpoints including protocol and port.
252
247
253
-
{:start="3"}
254
-
3. Certificate - The Kubernetes service account certificate used for the integration with Codefresh (base64 encoded).
255
-
256
-
{:start="4"}
257
-
4. Token - The Kubernetes service account token used for the integration with Codefresh (base64 encoded).
248
+
1. Name - Any name of your choosing, that will represent your cluster context in Codefresh. Do not use spaces, dots or other strange characters in the name.
249
+
1. Host - The full URL of the Kubernetes API endpoints including protocol and port.
250
+
1. Certificate - The Kubernetes service account certificate used for the integration with Codefresh (base64 encoded).
251
+
1. Token - The Kubernetes service account token used for the integration with Codefresh (base64 encoded).
To check the installation result type`venona status --verbose` and you will get a list of all installations.
122
122
123
+
###Installing behind a proxy
124
+
125
+
If you want to deploy the Codefresh runner on a Kubernetes cluster that doesn’t have direct access to`g.codefresh.io`, and has to go trough a proxy server to access`g.codefresh.io`, you will need to follow these additional steps:
126
+
127
+
*Step 1* - Follow the installation instructions of the previous section
128
+
129
+
*Step 2* - Run`kubectl edit deployment venona -ncodefresh-runtime` and add the proxy variables like this
*Step 3* - Add the following variables to your runtime.yaml, both under the`runtimeScheduler:` and under`dockerDaemonScheduler:` blocks inside the`envVars:` section
*Step 4* - Add`.firebaseio.com` to the allowed-sites of the proxy server
164
+
165
+
*Step 5* - Exec into the`dind` pod and run`ifconfig`
166
+
167
+
If the MTU value for`docker0` is higher than the MTU value of`eth0` (sometimes the`docker0` MTU is 1500, while`eth0` MTU is 1440 - you need to change this, the`docker0` MTU should be lower than`eth0` MTU
168
+
169
+
To fix this, edit the configmap in the codefresh-runtime namespace:
170
+
171
+
```
172
+
kubectl edit cm codefresh-dind-config -ncodefresh-runtime