-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: stop discovery errors from bootstrap process #1465
Conversation
@drivebyer do you know when this happens exactly ? old k8s version, a specific k8s flavor |
hi @vadmeste ,My k8s version is:
I think it is not about to k8s version, but about the
then you can see error message:
|
9c4502d
to
36d6f52
Compare
IMO we shouldn't panic, instead slowdown and retry here. This is a valid scenario, even if things are not running rightfully we must not panic here IMO. We should keep the operator reconcile this situation and retry for ever. |
If we retry here, the bootstrap process will hang unless the extension API server be healthy. IMO, the minio operator should not affected by the extension API server. The apiservice
|
We need to slowdown our rate of requests to the k8s api as well |
The current call trace is
Call |
36d6f52
to
8548982
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
hi @harshavardhana @dvaldivia @cniackz @pjuarezd @cesnietor is there any suggestion about this pr |
8548982
to
35cea2d
Compare
In test env, we got error sometimes:
We should not affect by extension API server during bootstrap process. The
ServerPreferredResources()
first returned result still contain recource info although err is not nil, see:https://github.com/kubernetes/client-go/blob/ba2fdddad18cb9d1822c00ddd5ba8cb0a428ebe7/discovery/discovery_client.go#L512-L536