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
A default managed repo is created automatically for every account.
10
10
The managed repo is private by default, allowing access only via Codefresh or using a Codefresh API token.
11
11
12
-
>You may be familiar with the popular open source Helm repository implementation called 'Chart Museum' that Codefresh sponsors. Codefresh managed repositories are based on, and therefore compatible with Chart Museum and it's unique features. For more info on Chart Museum:[https://github.com/kubernetes-helm/chartmuseum](https://github.com/kubernetes-helm/chartmuseum).
12
+
>You may be familiar with the popular open source Helm repository implementation called 'ChartMuseum' that Codefresh sponsors. Codefresh managed repositories are based on, and therefore compatible with ChartMuseum and it's unique features. For more info on ChartMuseum:[https://github.com/kubernetes-helm/chartmuseum](https://github.com/kubernetes-helm/chartmuseum).
13
+
13
14
14
15
##Helm repository integration
15
16
16
-
Your managedhelm repo will appear under the Helm repositories integration section just like any other Helm repository you might have added. You can manage Helm repo connections under*Account settings -> Integrations -> Helm repositories*.
17
+
Your managedHelm repo will appear under the Helm repositories integration section just like any other Helm repository you might have added. You can manage Helm repo connections under*Account settings -> Integrations -> Helm repositories*.
17
18
18
19
Note that you cannot delete the out-of-the-box managed repo that is created for you.
19
20
20
21
##Chart Repository URL
21
22
22
-
You can find your managed repository URL in the Helm integration section. The URL will take the form of:`https://h.cfcr.io/<accountname>/<reponame>`, where the default repo is called`default`.
23
-
This URL serve the`index.yaml` that Helm cli expects, and also supports the Chart Museum extended API, so you can push and delete charts as well.
23
+
You can find your managed repository URL in the Helm integration section. The URL will take the form of
24
24
25
-
##Codefresh Helm dashboards
25
+
`h.cfcr.io/<accountname>/<reponame>`
26
26
27
-
The Codefresh Helm Charts and Helm Releases dashboards are automatically configured to wotk with yourdefaultmangedreposo you can easily install charts and manage releases. For more information see:[Install chart from Helm repository](https://codefresh.io/docs/docs/new-helm/add-helm-repository/#install-chart-from-your-helm-repository) and[Helm release management](https://codefresh.io/docs/docs/new-helm/helm-releases-management/) articles.
27
+
where thedefault reponame is called`default`.
28
28
29
-
##Use Codefresh CLI for advanced management
29
+
This URL serve the`index.yaml` that Helm cli expects, and also supports the ChartMuseum extended API, so you can push and delete charts as well.
30
30
31
-
The Codefresh CLI can be used for advanced management of your managed repository. For more information on CLI support for Helm repos, see the 'Helm Repos' section in the CLI documentation:[https://codefresh-io.github.io/cli/helm-repos/](https://codefresh-io.github.io/cli/helm-repos/).
31
+
32
+
##Using your Repo
33
+
34
+
###Prerequisites
35
+
- Codefresh CLI. Install with`npm install -g codefresh`. See[here](https://codefresh-io.github.io/cli) for more info
This gives use the ability to push charts directly from Helm CLI, as well as the ability to use token-based authentication.
48
+
49
+
To authenticate to Codefresh via CLI, you can run
50
+
51
+
```
52
+
codefresh auth create-context --api-key=<token>
53
+
```
54
+
55
+
where`<token>` is a valid API Key obtained from the UI. For more instructions on how to obtain an API key, please see[here](https://codefresh-io.github.io/cli/getting-started/#authenticate).
56
+
57
+
Alternatively, you can set the`HELM_REPO_ACCESS_TOKEN` environment variable used by helm-push, which will take precedence over the authentication info set via CLI above:
58
+
59
+
```
60
+
export HELM_REPO_ACCESS_TOKEN=<token>
61
+
```
62
+
63
+
64
+
###Adding your repo as a local Helm repository
65
+
Run the following command to add your repo as a local Helm repository:
The managed Helm repository supports two modes of access level: Private and Public.
36
-
By default it is created as private which means read/write access is protected by Codefresh authentication.
37
-
You can switch the access level to Public which will make the repository accessibe to anonymouse users only*for read operations*. write operations always require authentication even when in public access mode.
107
+
The managed Helm repository supports two modes of access level: Private and Public.
108
+
109
+
By default it is created as private which means read/write access is protected by Codefresh authentication.
110
+
111
+
You can switch the access level to Public which will make the repository accessibe to anonymous users only*for read operations*. Write operations always require authentication even when in Public mode.
38
112
39
113
###Setting access level
40
114
41
115
Use the Codefresh CLI to toggle access level on a managed repo:
42
116
43
-
```bash
44
-
codefresh patch helm-repo mycfrepo -public
117
+
```
118
+
codefresh patch helm-repo <reponame> --public=true # Make Public
119
+
codefresh patch helm-repo <reponame> --public=false # Make Private
45
120
```
46
121
47
122
For more info see the relevant section in the Codefresh CLI documentation:[https://codefresh-io.github.io/cli/helm-repos/update-helm-repo/](https://codefresh-io.github.io/cli/helm-repos/update-helm-repo/).
48
123
49
-
##Working with Helm CLI
124
+
###Note on Public
50
125
51
-
###Add a Public repo toHelm
126
+
If your repo is configured tobe publicly accessible, you are not required to authenticate against Codefresh or install the helm-push plugin as described above (for read operations).
52
127
53
-
If your repo is settopublic access mode, you can use it just like any other HTTP Helm repository, so you can do:
128
+
You do not needtouse the special`cm://` protocol for adding your repo. You can add it using`https://`:
If your repo is set to private access mode (by default it is), then the Helm client needs to authenticate with Codefresh.
62
-
In order to authenticate, you can use Chart Museum's 'Helm Push' plugin. This is a Helm CLI plugin that adds support for authentication, and chart manipulation on top of the Helm standard CLI.
63
-
64
-
We highly recomment that you familiarize yourself with the Helm Push plugin, at:[https://github.com/chartmuseum/helm-push](https://github.com/chartmuseum/helm-push).
134
+
This URL can then be shared with others you wish to have access to your Helm charts.
65
135
66
-
###Add a Private repo to helm
136
+
##Use Codefresh CLI for advanced management
67
137
68
-
Before you continue, make sure you have the repo URL (see[here](#Chart Repository URL)forinstructions), and a Codefresh API toke (see[here](https://codefresh-io.github.io/cli/getting-started/#authenticate) for instructions).
138
+
The Codefresh CLI can be used for advanced management of your managed repository. For more information on CLI supportforHelm repos, see the 'Helm Repos' section in the CLI documentation:[https://codefresh-io.github.io/cli/helm-repos/](https://codefresh-io.github.io/cli/helm-repos/).
The Codefresh Helm Charts and Helm Releases dashboards are automatically configured to wotk with your default manged repo so you can easily install charts and manage releases. For more information see:[Install chart from Helm repository](https://codefresh.io/docs/docs/new-helm/add-helm-repository/#install-chart-from-your-helm-repository) and[Helm release management](https://codefresh.io/docs/docs/new-helm/helm-releases-management/) articles.
76
143
77
-
Notice the protocol is`cm://` instead of`https://` this indicates the custom authentication scheme supported by Chart Museum Helm Push plugin.