Closed JohnGarbutt closed 1 year ago
it looks like this is borken finding the error:
error: Failed to delete platform. Please contact Azimuth operators. phase: Failed updatedTimestamp: "2023-08-11T15:56:35Z" kind: List metadata: resourceVersion: "" selfLink: ""
Ok, great, that fixed the problem with not finding the error.
@JohnGarbutt
My personal opinion is that this should retry forever, with a backoff. As you said before, there is no way for a user to "re-trigger" the delete as Kubernetes already considers the resource as "marked for deletion", and IMHO requiring admin intervention in this case is rubbish.
However what you have implemented here is easy and works for now, so LGTM
On delete, there is no easy way for the user to retry, the admin has to go and delete job, after seeing a failed job alert. There is little cost in re-trying delete, in case it is some transient network error that might be fixed on a second try.