deckhouse / deckhouse/deckhouse
[global] check last patch version of core components before each release
Open
Nobody has claimed this yet.
priority/second
source/deckhouse-team
type/enhancement
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 162
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 653
Description
Preflight Checklist
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
Use case. Why is this important?
Because we don't check it now, we can't be sure, that new release won't create problems in clusters, that already known by community.
Proposed Solution
We need to check last patch version of core components (e.g. containerd, kubelet) before each release, to avoid known issues.
Additional Information
No response
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
The issue names no files, tests, or release entry point. Start by locating the release workflow and where containerd and kubelet versions are defined; done means each release checks their latest patch versions and prevents releases from using versions with known community-reported issues.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, infrastructure, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100