The lead master always seems to have the right creds on the k-c relation. Given that, a better workaround than the one in comment #3 would be:
juju run -u kubernetes-master/FOLLOWER_UNIT_NUMS 'relation-set -r $(relation-ids kube-control) creds='
This would ensure that *only* the master leader is providing creds to workers, and it's easier than manually changing kubeconfig files on each worker.
The lead master always seems to have the right creds on the k-c relation. Given that, a better workaround than the one in comment #3 would be:
juju run -u kubernetes- master/ FOLLOWER_ UNIT_NUMS 'relation-set -r $(relation-ids kube-control) creds='
This would ensure that *only* the master leader is providing creds to workers, and it's easier than manually changing kubeconfig files on each worker.