Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitfeb6197

Browse files
ThatAmatoGuya-mankinenkoNimRegev
authored
Support Article Migration (#673)
Migrating Support Articles from Zendesk to Main Documentation ---------Co-authored-by: a-mankinenko <81623122+a-mankinenko@users.noreply.github.com>Co-authored-by: NimRegev <nima.regev@codefresh.io>
1 parent4c7797e commitfeb6197

File tree

211 files changed

+7460
-691
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

211 files changed

+7460
-691
lines changed

‎_config.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -144,3 +144,5 @@ compress_html:
144144
startings:[head, body]
145145
ignore:
146146
envs:development
147+
148+
kb-cat:[Pipelines, Workflows, Ops, Artifacts & Insights, Settings, Runtimes, On-Prem, API, CLI, General]

‎_data/home-content.yml‎

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -296,5 +296,16 @@
296296

297297

298298

299-
299+
-title:"Knowledge Base"
300+
icon:images/home-icons/troubleshooting.svg
301+
url:''
302+
links:
303+
-title:Common Issues
304+
localurl:/docs/kb/common-issues
305+
-title:How To's
306+
localurl:/docs/kb/how-to
307+
-title:Troubleshooting
308+
localurl:/docs/kb/troubleshooting
309+
-title:Codefresh SLA Definitions
310+
localurl:/docs/kb/codefresh-sla-definitions
300311

‎_data/nav.yml‎

Lines changed: 8 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -618,59 +618,17 @@
618618
-title:ARM architecture support
619619
url:"/arm-support"
620620

621-
-title:Troubleshooting
622-
url:"/troubleshooting"
621+
-title:Knowledge Base
622+
url:"/kb"
623623
pages:
624624
-title:Common Issues
625625
url:"/common-issues"
626-
sub-pages:
627-
-title:Can't find your organization repositories
628-
url:"/cant-find-your-organization-repositories"
629-
-title:Can’t find your private repositories
630-
url:"/cant-find-your-private-repositories"
631-
-title:'Clone step failed: Command [git checkout $REVISION] exited with code [1]'
632-
url:"/git-clone-step-issue"
633-
-title:Handling commit messages with a quote character
634-
url:"/handling-commit-messages-with-quotes"
635-
-title:Docker image does not exist or no pull access
636-
url:"/the-docker-image-does-not-exist-or-no-pull-access"
637-
-title:'Build step: No such file or directory'
638-
url:"/build-step-no-such-file-or-directory"
639-
-title:No Dockerfile found
640-
url:"/no-dockerfile-found"
641-
-title:Failed to create container of image
642-
url:"/create-container-failure"
643-
-title:Failed to tag image
644-
url:"/could-not-tag-image"
645-
-title:Error Code 137
646-
url:"/error-code-137"
647-
-title:Too many requests
648-
url:"/dockerhub-rate-limit"
649-
-title:Restoring data from pre-existing image hangs on
650-
url:"/restoring-data-from-pre-existing-image-hangs-on"
651-
-title:Disabling codefresh caching mechanisms
652-
url:"/disabling-codefresh-caching-mechanisms"
653-
-title:Pinning codefresh.yml for multi-git triggers
654-
url:"/multi-git-triggers"
655-
-title:Workflow terminated by the system
656-
url:"/workflow-terminated-by-system"
657-
-title:cf_export limitations
658-
url:"/cf-export-limitations"
659-
-title:Validation port warnings
660-
url:"/validation-port-warnings"
661-
-title:Forbidden Kubernetes resources
662-
url:"/forbidden-cluster-resources"
663-
-title:How to use SSH keys in freestyle steps
664-
url:"using-ssh-keys"
665-
-title:Failed to get accounts clusters during workflow
666-
url:"/failed-to-get-accounts-clusters-during-workflow"
667-
-title:Paging issues for builds and images
668-
url:"/paging-issues-builds-images"
669-
-title:Deprecating personal Git integrations
670-
url:"/personal-git-deprecation"
671-
-title:GitOps runtimes
672-
url:"/runtime-issues"
673-
626+
-title:How Tos
627+
url:"/how-to"
628+
-title:Troubleshooting
629+
url:"/troubleshooting"
630+
-title:Codefresh SLA Definitions
631+
url:"/codefresh-sla-definitions"
674632

675633

676634
-title:Terms and Privacy Policy

‎_docs/installation/gitops/hybrid-gitops.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1305,4 +1305,4 @@ data:
13051305
[Monitoring & managing GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/)
13061306
[Add Git Sources to runtimes]({{site.baseurl}}/docs/installation/gitops/git-sources/)
13071307
[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration)
1308-
[Troubleshoot Hybrid Runtime installation]({{site.baseurl}}/docs/troubleshooting/runtime-issues/)
1308+
[Troubleshoot Hybrid Runtime installation]({{site.baseurl}}/docs/kb/articles/runtime-issues/)

‎_docs/installation/gitops/monitor-manage-runtimes.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -640,7 +640,7 @@ status:
640640

641641
A notification _Unable to communicate with a <runtime_name>_ or _Unable to communicate with two or more runtimes_ indicates a communication problem.
642642

643-
Refer to our [troubleshooting section]({{site.baseurl}}/docs/troubleshooting/runtime-issues/#unable-to-communicate-with-runtime-name-or-two-or-more-runtimes) for a list of possible causes and the corresponding corrective actions.
643+
Refer to our [troubleshooting section]({{site.baseurl}}/docs/kb/articles/runtime-issues/#unable-to-communicate-with-runtime-name-or-two-or-more-runtimes) for a list of possible causes and the corresponding corrective actions.
644644

645645

646646
### (Hybrid GitOps) View notifications in Activity Log

‎_docs/integrations/kubernetes.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -583,7 +583,7 @@ kubectl create clusterrolebinding default-admin --clusterrole cluster-admin --se
583583

584584
###Kubernetes cluster - using an external reverse proxy (edge case)
585585

586-
In caseyou'reusing 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.
586+
Ifyou areusing an external reverse proxy to manage inbound traffic to your Kubernetes API,for correct certificate setup, see[this article]({{site.baseurl}}/docs/kb/articles/verify-cluster-tls-ssl-configuration/).
587587

588588
###Multiple CAs in certificate chain
589589

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
title:403 Forbidden Error On Codefresh CLI Commands Within Build
3+
description:
4+
group:kb
5+
sub-group:articles
6+
toc:true
7+
kb:true
8+
ht:false
9+
common:false
10+
categories:[CLI, Pipelines]
11+
support-reviewed:2023-04-18 LG
12+
---
13+
14+
##Overview
15+
16+
When running a Codefresh CLI command from within a build, it fails with a 403 forbidden error.
17+
18+
##Details
19+
20+
Builds are run with the user context of the user who started it. So if any Codefresh CLI commands within a build fails with a 403 error, that means the user who started the build does not have the permissions to run this command.
21+
22+
1. Make sure this user is intended to have permissions to the actions performed by these CLI commands.
23+
2. As an account admin, make modifications to this user's team assignment and/or your account's permissions rules to grant this user access on relevant objects and actions.
24+
25+
##Related Items
26+
27+
[Configuring Access Control]({{site.baseurl}}/docs/administration/account-user-management/access-control/)
Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
---
2+
title:About reuseVolumeSelector options
3+
description:
4+
group:kb
5+
sub-group:articles
6+
toc:true
7+
kb:true
8+
ht:false
9+
common:false
10+
categories:[Runtimes]
11+
support-reviewed:2023-04-18 LG
12+
---
13+
14+
##Overview
15+
16+
The behavior of how the volumes are reused depends on volume selector configuration.
17+
18+
`reuseVolumeSelector: 'codefresh-app,io.codefresh.accountName'`
19+
20+
That means that a determined volume can be used by any pipeline of your account.
21+
22+
`reuseVolumeSelector: 'codefresh-app,io.codefresh.accountName,pipeline_id'`
23+
24+
That means that a determined PV can be used only by a specific pipeline.
25+
26+
##Details
27+
28+
For approach_codefresh-app,io.codefresh.accountName_ :
29+
30+
* Benefit: less PVs --> lower cost (since any PV can be used by any pipeline, then, the cluster would need to keep less PVs in its pool of PVs for Codefresh)
31+
* Downside: since the PV can be used by any pipeline, then, the PVs could have assets and info from different pipelines, thus reducing the probability of cache,
32+
33+
For approach_codefresh-app,io.codefresh.accountName,pipeline_id_ :
34+
35+
* Benefit: more probability of cache (no "spam" from other pipelines)
36+
* Downside: more PVs to keep (higher cost)
37+
38+
###How-to change the reuseVolumeSelector in your Runtime Environment
39+
40+
To make the changes in your Runtime Environment, you will need to use the
41+
[Codefresh CLI.](https://codefresh-io.github.io/cli/installation/)
42+
43+
1. Get your Runtime Environment:
44+
45+
```shell
46+
codefresh get re<name> -o yaml> spec.yaml
47+
```
48+
49+
1. Modify the reuseVolumeSelectorin the the downloaded file,in the example
50+
below we change it to per-pipeline mode:
51+
52+
``` yaml
53+
...
54+
pvcs:
55+
dind:
56+
...
57+
reuseVolumeSelector:'codefresh-app,io.codefresh.accountName, **pipeline_id**'
58+
...
59+
```
60+
61+
1. Patch your RE using the following CLI command:
62+
63+
```shell
64+
codefresh patch re -f spec.yaml
65+
```
66+
67+
## Related items
68+
69+
[Volume Reusage Policy]({{site.baseurl}}/docs/installation/codefresh-runner/#volume-reuse-policy)
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
title:Attempting to clone from a repo but access is denied
3+
description:
4+
group:kb
5+
sub-group:articles
6+
toc:true
7+
kb:true
8+
ht:false
9+
common:false
10+
categories:[Pipelines]
11+
support-reviewed:2023-04-18 LG
12+
---
13+
14+
##Overview
15+
16+
Access is denied when using a clone step
17+
18+
##Details
19+
20+
Insufficient access in the Git integration, or incorrect Git integration
21+
used.:
22+
23+
* Ensure that the account used in Integrations has the appropriate access.
24+
* Ensure that in your clone step, you are using the right name for the git provider.
25+
* If the account used to set up integration is no longer active, you will need to remove the current integration and replace it.
26+
27+
1. Go to your[Account Settings -> Integrations -> Git](https://g.codefresh.io/account-admin/account-conf/integration/git).
28+
* If you do not have access, please contact one of your team's admins
29+
2. Update the previous integration with a new token, or delete the previous integration
30+
3. Create a new integration
31+
32+
>Note: When deleting a git integration, you may get an error saying the integration cannot be deleted while other objects are using it. This means an existing pipeline is referencing the integration. Please refer to[How-to: Update Trigger Git Context]({{site.baseurl}}/docs/kb/articles/update-trigger-git-context) on how to find and modify these existing references.
Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
title:Account invitation not permitting login
3+
description:
4+
group:kb
5+
sub-group:articles
6+
toc:true
7+
kb:true
8+
ht:false
9+
common:false
10+
categories:[Settings, General]
11+
support-reviewed:2023-04-18 LG
12+
---
13+
14+
##Overview
15+
16+
1. Accepting an invite does not allow you to access the inviting account.
17+
2. Accepting an invite does not work, and fails to let you log in.
18+
19+
##Details
20+
21+
The account is not correctly linked.
22+
23+
1. Ensure that the email account you're logging in with is the same as the email address used for the invite.
24+
2. Log out of any previous sessions with the relevant identity provider and if need be, try a different browser or a private/incognito window.
25+
3. If you are able to log in but don't see the inviting account, your user may be under multiple accounts. If this is the case, you can switch between available accounts via the user menu drop-down in the upper right-hand corner.
26+
27+
_Notes_ In the event that this issue persists, please[contact our supportteam](https://support.codefresh.io/hc/en-us/requests/new) with as many details as you have.

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp