linkerd / linkerd/website

Update docs for 2.12.0-stable

Open
#1,400 3 comments 0 reactions 1 assignee View on GitHub

@jeremychase is already working on this.

Since Aug 20, 2022.

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

Description

This issue is a high-level task list. Adding things to this list is OK; so is creating other issues and making this issue depend on them if you have something more complex.

- [x] Have a clean source of truth for all the 2.12 docs – `shared/docs/2.12` should be this now.
- [x] #1432
- [x] #1403
- [x] #1404
- [x] #1405
- [x] #1406
- [x] #1407
- [x] #1408
- [x] #1409
- [x] #1410
- [x] #1411
- [ ] Trust anchors can be RSA-signed now; does this need doc?
- [x] [Update notes](https://github.com/linkerd/website/pull/1244/files#diff-9f3e30714d307bfc51b63c0f2f643815ade093caef357b6c1d697a6f46205123
) say the dataplane won't incur in downtime but that's only true if there are no new services added into the cluster during the migration of the controlplane chart
- [x] [Update notes](https://github.com/linkerd/website/pull/1244/files#diff-9f3e30714d307bfc51b63c0f2f643815ade093caef357b6c1d697a6f46205123
) also need to mention that CRs such as ServiceProfiles, TrafficSplits and the policy CRs need to be saved before removing the `linkerd2` chart and re-added after creating the `linkerd-crds` chart for 2.12

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.