From 2af7184f91455a47de6025988c05c0c54b4353de Mon Sep 17 00:00:00 2001 From: alinashklyar Date: Tue, 6 Jan 2026 15:08:16 +0200 Subject: [PATCH 1/2] update docs --- .../kubernetes/custom-kubectl-commands.md | 22 +------------------ _docs/pipelines/what-is-the-codefresh-yaml.md | 2 ++ 2 files changed, 3 insertions(+), 21 deletions(-) diff --git a/_docs/deployments/kubernetes/custom-kubectl-commands.md b/_docs/deployments/kubernetes/custom-kubectl-commands.md index 620506055..aa0df83a8 100644 --- a/_docs/deployments/kubernetes/custom-kubectl-commands.md +++ b/_docs/deployments/kubernetes/custom-kubectl-commands.md @@ -20,26 +20,6 @@ In the current Codefresh implementation, this expands to `/codefresh/volume/sens When you use custom `kubectl` commands, it is your responsibility to template your manifests using any of the available options. To employ Codefresh for templating, it is better to use the dedicated [cf-deploy-kubernetes step]({{site.baseurl}}/docs/ci-cd-guides/kubernetes-templating/), which provides simple templating capabilities. -## Using the Codefresh kubectl image - -Codefresh already offers a public Docker image with `kubectl` at [https://hub.docker.com/r/codefresh/kubectl/tags](https://hub.docker.com/r/codefresh/kubectl/tags){:target="\_blank"}. You can choose a specific version of `kubectl` with the appropriate tag or just select `latest` for the most up-to-date version. - -`YAML` -{% highlight yaml %} -{% raw %} -version: '1.0' -steps: - MyCustomKubectlCommands: - title: Running Kubectl - image: codefresh/kubectl:1.13.3 - commands: - - echo $CF_KUBECONFIG_PATH - - kubectl help -{% endraw %} -{% endhighlight %} - -If you run the pipeline, you can see the help options for `kubectl`. - ## Getting a config context The important thing to know when running custom `kubectl` commands is that Codefresh automatically sets up @@ -183,4 +163,4 @@ In the example above, we select one of the clusters in each deployment step, and - \ No newline at end of file + diff --git a/_docs/pipelines/what-is-the-codefresh-yaml.md b/_docs/pipelines/what-is-the-codefresh-yaml.md index 0a26540d5..48fcc98fb 100644 --- a/_docs/pipelines/what-is-the-codefresh-yaml.md +++ b/_docs/pipelines/what-is-the-codefresh-yaml.md @@ -234,6 +234,8 @@ steps: Notice that Codefresh also provides the following variables that allow you change your script/applications according to the retry attempts: * `CF_CURRENT_ATTEMPT` contains the number of current retry attempt. +> **Note:** This variable is always contextual to the exact step and does not reflect the parent state + * `CF_MAX_ATTEMPTS` contains all the number of total attempts defined. The retry mechanism is available for all kinds of [steps]({{site.baseurl}}/docs/pipelines/steps/). From a7399095541d6bab666488d802a86b1f5307402d Mon Sep 17 00:00:00 2001 From: alinashklyar Date: Tue, 13 Jan 2026 11:10:08 +0200 Subject: [PATCH 2/2] docs change --- _docs/pipelines/what-is-the-codefresh-yaml.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/_docs/pipelines/what-is-the-codefresh-yaml.md b/_docs/pipelines/what-is-the-codefresh-yaml.md index 48fcc98fb..45f87e5e3 100644 --- a/_docs/pipelines/what-is-the-codefresh-yaml.md +++ b/_docs/pipelines/what-is-the-codefresh-yaml.md @@ -234,12 +234,13 @@ steps: Notice that Codefresh also provides the following variables that allow you change your script/applications according to the retry attempts: * `CF_CURRENT_ATTEMPT` contains the number of current retry attempt. -> **Note:** This variable is always contextual to the exact step and does not reflect the parent state * `CF_MAX_ATTEMPTS` contains all the number of total attempts defined. The retry mechanism is available for all kinds of [steps]({{site.baseurl}}/docs/pipelines/steps/). +> **Note:** `CF_CURRENT_ATTEMPT` variable is always contextual to the exact step and does not reflect the parent state + ## Escaping strings If you want to use strings inside your pipeline that create conflicts with the Codefresh syntax parser (for example they are YAML themselves) you need