Why only retry on 401s and 403s during runner registration?

[postsa]

I was debugging an issue where runners failed to register after refetching auth tokens and noticed that retry only happens on 401s and 403s.

Here is the relevant pull request #3377.

I’m curious why only client error is retried (@nikola-jokic or @rentziass).

Additionally, am I correct in assuming that if an ephemeral error occurs when registering the runner that the runner’s listener and associated CRDS will be removed by the controller?

https://github.com/actions/actions-runner-controller/blame/68787beab5396085227c16e0b2cd472c0520d435/github/actions/client.go#L1134C4-L1140C4