Create integration test for upgrades from the previous edge
Open
Nobody has claimed this yet.
area/test
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
Currently we have integration tests for checking upgrades from the latest stable release, both through the CLI and Helm. We should add another set to do the same for the latest edge release, to catch issues like #4471, where we missed to document a change in the `values.yaml`.
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 by locating the existing integration tests for upgrades from the latest stable release through the CLI and Helm, then identify how the latest edge release is selected. Add equivalent edge-upgrade coverage, including the values.yaml compatibility case, and run the integration test suite to verify both paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- devops, release, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100