-
Notifications
You must be signed in to change notification settings - Fork 501
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
Add case for kube proxy #503
Conversation
LGTM |
tests/failover.go
Outdated
if err != nil { | ||
return err | ||
} | ||
glog.V(4).Infof("all clusters are available.") | ||
return nil |
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.
ditto
if err != nil { | ||
glog.Infof("can't find controllerManager in node:%s", faultNode) | ||
slack.NotifyAndPanic(fmt.Errorf("can't find kube-controller-manager in k8s cluster")) |
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.
@xiaojingchen ptal
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.
@onlymellb the controller pod may be not in the master, this case is normal
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.
no need to panic
if err != nil { | ||
glog.Infof("can't find scheduler in node:%s", faultNode) | ||
slack.NotifyAndPanic(fmt.Errorf("can't find kube-scheduler in k8s cluster")) |
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.
@xiaojingchen ptal
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.
scheduler pod can run in work node
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.
If the returned err is not nil, it means that search this component in kube-system namespace has failed. If the master node does not have this component, the returned err is nil. Therefore, it is necessary to send an alarm and panic when the returned error is not nil.
@onlymellb please address @xiaojingchen comments |
…perator into add-case-for-kube-proxy
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
/run-e2e-tests |
@onlymellb |
fixed by: #556 |
* add helm offline doc * update format * Apply suggestions from code review Co-authored-by: Ran <huangran@pingcap.com> * Apply suggestions from code review Co-authored-by: Ran <huangran@pingcap.com> Co-authored-by: Ran <huangran@pingcap.com>
What problem does this PR solve?
What is changed and how it works?
Check List
Tests
Code changes
Side effects
Related changes
Does this PR introduce a user-facing change?: