kubernetes-sigs/cluster-api

Deleting retries history during KCP remediation

Aberta

#10.911 aberto em 19 de jul. de 2024

 (5 comentários) (0 reação) (0 responsável)Go (1.532 forks)auto 404
area/control-planehelp wantedkind/bugpriority/important-longtermtriage/accepted

Métricas do repositório

Stars
 (4.267 estrelas)
Métricas de merge de PR
 (Métricas PR pendentes)

Description

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

Guia do colaborador