Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a Helm repo to host the Linkerd Helm chart #3365

Closed
ihcsim opened this issue Sep 3, 2019 · 3 comments · Fixed by linkerd/website#502
Closed

Create a Helm repo to host the Linkerd Helm chart #3365

ihcsim opened this issue Sep 3, 2019 · 3 comments · Fixed by linkerd/website#502
Assignees
Labels
priority/P0 Release Blocker

Comments

@ihcsim
Copy link
Contributor

ihcsim commented Sep 3, 2019

Create a new Helm repo on GCS to host the Linkerd Helm chart. Users will install the Helm chart by interacting with this repo:

helm repo add linkerd https://linkerd.storage.googleapis.com/ # if the bucket name is available
helm install <prefix>/linkerd2  # not sure what <prefix> should be; might be optional

Related #3256.

@ihcsim ihcsim added the priority/P0 Release Blocker label Sep 3, 2019
@ihcsim ihcsim added this to To do in 2.6 - Release via automation Sep 3, 2019
@grampelberg
Copy link
Contributor

WDYT about just putting this into run.linkerd.io? Adding the chart tarballs to the website repo isn't super amazing, but at least we'd get it all working in the same flow.

@ihcsim
Copy link
Contributor Author

ihcsim commented Sep 3, 2019

So place the tar file at https://run.linkerd.io/charts/linkerd2.tar.gz? And then run something like:

helm repo add linkerd https://run.linkerd.io/charts
helm install linkerd/linkerd2

Sure, I don't have a strong preference.

@grampelberg
Copy link
Contributor

Yup, that's my thinking.

@alpeb alpeb self-assigned this Sep 4, 2019
alpeb added a commit to linkerd/website that referenced this issue Sep 5, 2019
This adds the Helm repos `https://run.linkerd.io/edge` and
`https://run.linkerd.io/stable`.

So the user would install the stable chart with:
```bash
helm repo add linkerd-stable https://run.linkerd.io/stable
helm install --set blah blah linkerd-stable/linkerd2
```

So the user would install the edge chart with:
```bash
helm repo add linkerd-edge https://run.linkerd.io/edge
helm install --set blah blah linkerd-edge/linkerd2
```

Both repos can coexist in the same Helm environment.

I've updated the `install-helm.md` doc accordingly.

The `index.yaml` and `linkerd2-0.1.0.tgz` files were generated with the
`bin/helm -stable|edge` command added in linkerd/linkerd#3292

Signed-off-by: Alejandro Pedraza Borrero <alejandro@buoyant.io>
@alpeb alpeb moved this from To do to Review in progress in 2.6 - Release Sep 5, 2019
2.6 - Release automation moved this from Review in progress to Done Sep 16, 2019
alpeb added a commit to linkerd/website that referenced this issue Sep 16, 2019
* Fixes linkerd/linkerd2#3365

This adds the Helm repos `https://helm.linkerd.io/edge` and
`https://helm.linkerd.io/stable`.

So the user would install the stable chart with:
```bash
helm repo add linkerd https://run.linkerd.io/stable
helm install --set blah blah linkerd/linkerd2
```

or
```bash
helm repo add linkerd-edge https://run.linkerd.io/edge
helm install --set blah blah linkerd-edge/linkerd2
```

Both repos can coexist in the same Helm environment.

I've updated the `install-helm.md` doc accordingly.

I also added an new paragraph about Helm v2 `--namespace` support.

Signed-off-by: Alejandro Pedraza Borrero <alejandro@buoyant.io>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority/P0 Release Blocker
Projects
No open projects
2.6 - Release
  
Done
Development

Successfully merging a pull request may close this issue.

3 participants