k0sproject/k0smotron

Include testing logic per update strategy

Closed

#1,541 opened on Aug 6, 2026

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Go (78 forks)auto 404
cluster-apigood first issue

Repository metrics

Stars
 (721 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently, we are running same test spec for every update strategy which is good in terms of no code-duplications but we are not adding custom checks depending on the strategy.

For instance, inplace upgrade should check there is no mahcine recreated, RecreateDeleteFirst should check there are no more machines than desired..etc. Probably some check injection would be great in order to avoid if-elses depending on the strategy

Contributor guide

Research direction
Review the test files that cover update strategies. Identify how strategy specific behavior is currently tested and where custom checks could be added. Consider refactoring to support per strategy test logic without code duplication.
Tech stack
go
Domain
testingbackend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75