kubernetes: Restarting kubelet with new node labels doesn't update labels for node

kubelet version: 1.2.4

Steps to reproduce:

start kubelet with some labels using the --node-labels flag
wait for the node to register itself with the master
restart kubelet with a different set of labels

Expected result: kubectl get no --show-labels shows the node with the updated labels

Actual result: kubectl get no --show-labels shows the node with the original labels

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 3
Comments: 17 (14 by maintainers)

Most upvoted comments

I would do this if we decide to persist node labels at last.

adohe-zz on Jul 27, 2016

I don’t think this can be a release blocker since it’s not a bug. This feature functions as documented. fixing this issue is an additional feature, not a bugfix.

This can’t break customers since it’s been as-is (and as-documented) for multiple releases now.

I see no reason this additional feature (which requires additional kubelet persistence and has zero work thusfar) should go in post-feature freeze and shouldn’t be targeted at 1.6.

Happy to be corrected if I’m misunderstanding anything

euank on Nov 18, 2016