Verify the Helm Upgrade procedure still works
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 221
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 1
Description
Currently the docs prscribe that helm upgrade linkerd2 linkerd/linkerd2 --reuse-values should be used when ugrading. However this does not work at the moment. When upgrading from 2.6 to edge things break and helm is complaining that its missing values. We need to investigate what is happening and what is the proper upgrade process as quite a bit of things have moved around/changed in the charts. For reference this works:
helm upgrade linkerd2 \
--set-file global.identityTrustAnchorsPEM=ca.crt \
--set-file identity.issuer.tls.crtPEM=issuer.crt \
--set-file identity.issuer.tls.keyPEM=issuer.key \
--set identity.issuer.crtExpiry=$exp \
linkerd-edge/linkerd2 --atomic
Also some more information around the use of --reuse-values and --reset-values can be found right here:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the documentation that describes the Helm upgrade procedure and reproduce the reported upgrade from 2.6 to edge using the documented command. Compare it with the working command and Helm's missing-values error; done means the correct upgrade process, including the relevant values behavior, is documented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100