Comment 12 for bug 1905058

I just reproduced this. It looks like it only occurs if there is a kubernetes-master follower with stale creds, and the follower's unit ID is *higher* than that of the current leader. e.g. kubernetes-master/0 is current leader, kubernetes-master/1 is former leader with stale creds. The higher unit ID takes precedence because of the merge logic in interface-kube-control[1].

The workaround from #8 worked for me, although it did take a couple minutes for the workers to update their tokens.

I think Felipe is on the right track in comment #1. Clearing the stale creds from non-leaders is probably the easiest and quickest solution.

[1]: https://github.com/charmed-kubernetes/interface-kube-control/blob/ea90ca566da63750ab90bc1443c77d912abf6d58/requires.py#L57-L58