Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Cordoning & Draining all nodes healthy nodes #54

Open
sstarcher opened this issue Oct 15, 2019 · 2 comments
Open

Cordoning & Draining all nodes healthy nodes #54

sstarcher opened this issue Oct 15, 2019 · 2 comments

Comments

@sstarcher
Copy link
Contributor

I installed draino to test it out and it immeditatly cordoned all of my nodes. After turning on debug the logs are as follows. It was installed via the helm chart in a Kubernetes 1.14.6 cluster.

draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.056Z	DEBUG	kubernetes/eventhandler.go:114	Cordoning	{"node": "ip-10-40-1-42.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.056Z	INFO	kubernetes/eventhandler.go:123	Cordoned	{"node": "ip-10-40-1-42.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.056Z	INFO	kubernetes/eventhandler.go:132	Scheduled drain	{"node": "ip-10-40-1-42.us-west-2.compute.internal", "after": "2019-10-15T15:01:23.937Z"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.056Z	DEBUG	kubernetes/eventhandler.go:114	Cordoning	{"node": "ip-10-40-6-32.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.056Z	INFO	kubernetes/eventhandler.go:123	Cordoned	{"node": "ip-10-40-6-32.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.056Z	INFO	kubernetes/eventhandler.go:132	Scheduled drain	{"node": "ip-10-40-6-32.us-west-2.compute.internal", "after": "2019-10-15T15:11:23.937Z"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.057Z	DEBUG	kubernetes/eventhandler.go:114	Cordoning	{"node": "ip-10-40-8-50.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.057Z	INFO	kubernetes/eventhandler.go:123	Cordoned	{"node": "ip-10-40-8-50.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.057Z	INFO	kubernetes/eventhandler.go:132	Scheduled drain	{"node": "ip-10-40-8-50.us-west-2.compute.internal", "after": "2019-10-15T15:21:23.937Z"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.057Z	DEBUG	kubernetes/eventhandler.go:114	Cordoning	{"node": "ip-10-40-11-78.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.057Z	INFO	kubernetes/eventhandler.go:123	Cordoned	{"node": "ip-10-40-11-78.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.058Z	INFO	kubernetes/eventhandler.go:132	Scheduled drain	{"node": "ip-10-40-11-78.us-west-2.compute.internal", "after": "2019-10-15T15:31:23.937Z"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.058Z	DEBUG	kubernetes/eventhandler.go:114	Cordoning	{"node": "ip-10-40-2-117.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.058Z	INFO	kubernetes/eventhandler.go:123	Cordoned	{"node": "ip-10-40-2-117.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.058Z	INFO	kubernetes/eventhandler.go:132	Scheduled drain	{"node": "ip-10-40-2-117.us-west-2.compute.internal", "after": "2019-10-15T15:41:23.937Z"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.058Z	DEBUG	kubernetes/eventhandler.go:114	Cordoning	{"node": "ip-10-40-6-253.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	INFO	kubernetes/eventhandler.go:123	Cordoned	{"node": "ip-10-40-6-253.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	INFO	kubernetes/eventhandler.go:132	Scheduled drain	{"node": "ip-10-40-6-253.us-west-2.compute.internal", "after": "2019-10-15T15:51:23.937Z"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	DEBUG	kubernetes/eventhandler.go:114	Cordoning	{"node": "ip-10-40-1-213.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	INFO	kubernetes/eventhandler.go:123	Cordoned	{"node": "ip-10-40-1-213.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	INFO	kubernetes/eventhandler.go:132	Scheduled drain	{"node": "ip-10-40-1-213.us-west-2.compute.internal", "after": "2019-10-15T16:01:23.937Z"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	DEBUG	kubernetes/eventhandler.go:114	Cordoning	{"node": "ip-10-40-3-232.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	INFO	kubernetes/eventhandler.go:123	Cordoned	{"node": "ip-10-40-3-232.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	INFO	kubernetes/eventhandler.go:132	Scheduled drain	{"node": "ip-10-40-3-232.us-west-2.compute.internal", "after": "2019-10-15T16:11:23.937Z"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	DEBUG	kubernetes/eventhandler.go:114	Cordoning	{"node": "ip-10-40-5-12.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	INFO	kubernetes/eventhandler.go:123	Cordoned	{"node": "ip-10-40-5-12.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	INFO	kubernetes/eventhandler.go:132	Scheduled drain	{"node": "ip-10-40-5-12.us-west-2.compute.internal", "after": "2019-10-15T16:21:23.937Z"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	DEBUG	kubernetes/eventhandler.go:114	Cordoning	{"node": "ip-10-40-9-88.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	INFO	kubernetes/eventhandler.go:123	Cordoned	{"node": "ip-10-40-9-88.us-west-2.compute.internal"}
draino-558558fbb-d8mlr:draino 2019-10-15T14:51:24.135Z	INFO	kubernetes/eventhandler.go:132	Scheduled drain	{"node": "ip-10-40-9-88.us-west-2.compute.internal", "after": "2019-10-15T16:31:23.937Z"}```
@sstarcher
Copy link
Contributor Author

The current version used by the helm chart considers all states to be bad states. Do you have a recommended set of states that we can put in the helm chart?

@bilalcaliskan
Copy link

actually it is not, as seen in here. I am using Draino with node-problem-detector and belows are working fine in my case.

  • KernelDeadlock
  • ReadonlyFilesystem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sstarcher @bilalcaliskan