Comment 7 for bug 1905058

I was able to get the env like i wanted in comment #3, but no matter what combination of "old" vs "new" creds were on the kube-control relation of "leader" vs "follower" master units, all my workers had the "new" creds in their kubelet kubeconfig files.

I'm moving this to Incomplete until we can get more details on a failed env. If possible, please attach a juju crashdump; hopefully we'll find more clues in the auth-webhook and unit debug-hook logs as to why some workers are insistent on holding onto old creds.