k0sproject/k0smotron

Include testing logic per update strategy

クローズ

#1,541 opened on 2026/08/06

 (5 件のコメント) (0 件のリアクション) (0 人の担当者)Go (78 件のフォーク)auto 404
cluster-apigood first issue

Repository metrics

Stars
 (721 個のスター)
PR merge metrics
 (PR metrics pending)

説明

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

コントリビューターガイド