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

kubelet drain script fails when there is a daemon set deployed on worker #181

Closed
alex-slynko opened this Issue Feb 28, 2018 · 3 comments

Comments

Projects
None yet
4 participants
@alex-slynko
Member

alex-slynko commented Feb 28, 2018

Draing stderr log

 node "0c974061-bad5-4810-bcee-52a300aa76e1" cordoned
 Kubelet drain failed

Drain stdout log

error: unable to drain node "0c974061-bad5-4810-bcee-52a300aa76e1", aborting command...

There are pending nodes to be drained:
  0c974061-bad5-4810-bcee-52a300aa76e1
error: daemonsets.extensions "my-fabulous-node-agent" is forbidden: User "kubelet-drain" cannot get daemonsets.extensions in the namespace "fabulous-infrastructure": fabulous-node-agent-mgg9t, fabulous-node-agent-mgg9t
@cf-gitbot

This comment has been minimized.

cf-gitbot commented Feb 28, 2018

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/155595169

The labels on this github issue will be updated when the story is started.

@alex-slynko

This comment has been minimized.

Member

alex-slynko commented Feb 28, 2018

From documentation

Drain node "foo", even if there are pods not managed by a ReplicationController, ReplicaSet, Job, DaemonSet or StatefulSet on it.
 kubectl drain foo --force

@tvs tvs assigned tvs and unassigned akshaymankar Mar 1, 2018

@tvs

This comment has been minimized.

Member

tvs commented Mar 1, 2018

Should be fixed as of df25069

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment