add doc for wiping etcd state (#5939)
This commit is contained in:
		
							parent
							
								
									a7acfa8270
								
							
						
					
					
						commit
						4c4d56bfc0
					
				|  | @ -471,6 +471,19 @@ kubeadm reset | ||||||
| If you wish to start over simply run `kubeadm init` or `kubeadm join` with the | If you wish to start over simply run `kubeadm init` or `kubeadm join` with the | ||||||
| appropriate arguments. | appropriate arguments. | ||||||
| 
 | 
 | ||||||
|  | **Note**: `kubeadm reset` will not delete any etcd data if external etcd is used.  | ||||||
|  | This means that if you run `kubeadm init` again using the same etcd endpoints, you  | ||||||
|  | will see state from previous clusters. To wipe etcd data after reset, it is  | ||||||
|  | recommended you use a client like `etcdctl`, such as: | ||||||
|  | 
 | ||||||
|  | ``` | ||||||
|  | etcdctl del "" --prefix | ||||||
|  | ```  | ||||||
|  | 
 | ||||||
|  | See  | ||||||
|  | [their documentation](https://github.com/coreos/etcd/tree/master/etcdctl) for more  | ||||||
|  | information. | ||||||
|  | 
 | ||||||
| ## Upgrading | ## Upgrading | ||||||
| 
 | 
 | ||||||
| Instructions for upgrading kubeadm clusters are available for: | Instructions for upgrading kubeadm clusters are available for: | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue