kubernetes-sigs/cluster-api

Deleting retries history during KCP remediation

開放

#10,911 建立於 2024年7月19日

 (5 則留言) (0 個反應) (0 位負責人)Go (1,532 個分叉)auto 404
area/control-planehelp wantedkind/bugpriority/important-longtermtriage/accepted

倉庫指標

星標
 (4,267 顆星)
PR 合併指標
 (平均合併 3天 1小時) (30 天內合併 114 個 PR)

描述

What steps did you take and what happened?

At a random moment, during the KCP remediation process, a machine is created without the history of previous retries. The remedation-in-progress annotation hangs on the KCP resource and is deleted after some time.

It turns out that the retry history is not saved.

What did you expect to happen?

Retry history is saved

Cluster API version

1.7

Kubernetes version

1.27.14

Anything else you would like to add?

I think that this happens when the resource is patched, and at the next stage of reconciliation the control plane is listed without these annotations.

Label(s) to be applied

/kind bug /area control-plane

貢獻者指南