fix(operator): do not panic if cannot set GOMAXPROCS

[squakez]

Closes #4299

Release Note

fix(operator): do not panic if cannot set GOMAXPROCS

[squakez]

@astefanutti I'd like your opinion on this one. I have the feeling we should be safe by just logging the error (then it will be up to the operator installer to figure it out how to solve this problem to improve concurrency). In this way we at least let the operator run in situations where we cannot control the cluster (ie, the github actions which suddenly stopped to work).

[squakez]

Merging, so that we can keep the development and other PRs ahead. We can keep discussing in #4299

[astefanutti]

@astefanutti I'd like your opinion on this one. I have the feeling we should be safe by just logging the error (then it will be up to the operator installer to figure it out how to solve this problem to improve concurrency). In this way we at least let the operator run in situations where we cannot control the cluster (ie, the github actions which suddenly stopped to work).

@squakez sorry for the late reply, this felt under my radar. Error logging looks like a pragmatic approach. I think situations where this could lead to nasty issues are very seldom. This would ideally go away anyway with golang/go#33803.