linkerd / linkerd/website

Include upgrade instructions in `run.linkerd.io/public/install`

Open
#419 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
60
Forks
221
Avg merge
4h 32m
Merged PRs (30d)
1

Description

This is a feature request that came from discussion in [#3018 in the Linkerd2 repo](https://github.com/linkerd/linkerd2/issues/3018).

Currently, when a user runs `curl https://run.linkerd.io/install-edge | sh`, the confirmation text does not mention `linkerd upgrade`. This can be confusing as the "Now run:" spelled out in the confirmation text will not work for users if they already have Linkerd installed.

`run.linkerd.io/public/install` should have these changes:

When a user runs `curl https://run.linkerd.io/install-edge | sh`

* Check for linkerd in the user's path when they download Linkerd
* If linkerd is NOT in the user's path, add link to upgrade docs at the end of output
* If linkerd IS in the user's path, add link to upgrade docs before the "Now run:" section.

```bash
Linkerd was successfully installed 🎉

Upgrading? https://linkerd.io/2/tasks/upgrade/

Installing for the first time? Add the linkerd CLI to your path with:

export PATH=$PATH:$HOME/.linkerd2/bin

[rest of output stays the same]
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at run.linkerd.io/public/install and inspect the output produced by `curl https://run.linkerd.io/install-edge | sh`. Verify the first-install and existing-CLI cases by checking whether `linkerd` is on PATH; done means the upgrade URL appears in the requested position while the remaining output stays unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
cli
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.