diff options
| author | youyongsong <youyongsong@gmail.com> | 2018-06-09 23:48:10 +0800 |
|---|---|---|
| committer | youyongsong <youyongsong@gmail.com> | 2018-06-09 23:48:10 +0800 |
| commit | 866b7c8fcc1bc71e3a08b82dcc38f63ade509e44 (patch) | |
| tree | efb29b5174cc938a5689d5edacbc87bb88a6aca3 | |
| parent | 477ece3f466a9d5f9e043a4f38ca2c1b5074ede5 (diff) | |
system:bootstrappers should be the right group.
| -rw-r--r-- | keps/sig-cluster-lifecycle/draft-20180130-kubeadm-join-master.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/keps/sig-cluster-lifecycle/draft-20180130-kubeadm-join-master.md b/keps/sig-cluster-lifecycle/draft-20180130-kubeadm-join-master.md index 10554064..15fd846a 100644 --- a/keps/sig-cluster-lifecycle/draft-20180130-kubeadm-join-master.md +++ b/keps/sig-cluster-lifecycle/draft-20180130-kubeadm-join-master.md @@ -280,7 +280,7 @@ existing `kubeadm join` flow: in `kube-system` namespace. > This requires to grant access to the above configMap for - `system:node-bootstrapper` group (or to provide the same information + `system:bootstrappers` group (or to provide the same information provided in a file like in 1.). 2. Check if the cluster is ready for joining a new master node: |
