1. minikube node stop
停止集群中一个 node 节点
minikube node stop [flags]
1.1. 从父命令继承的选项
--add_dir_header If true, adds the file directory to the header of the log messages
--alsologtostderr log to standard error as well as files
-b, --bootstrapper string The name of the cluster bootstrapper that will set up the Kubernetes cluster. (default "kubeadm")
-h, --help
--log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
--log_dir string If non-empty, write log files in this directory
--log_file string If non-empty, use this log file
--log_file_max_size uint Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
--logtostderr log to standard error instead of files
--one_output If true, only write logs to their native severity level (vs also writing to each lower severity level)
-p, --profile string The name of the minikube VM being used. This can be set to allow having multiple instances of minikube independently. (default "minikube")
--skip_headers If true, avoid header prefixes in the log messages
--skip_log_headers If true, avoid headers when opening log files
--stderrthreshold severity logs at or above this threshold go to stderr (default 2)
--user string Specifies the user executing the operation. Useful for auditing operations executed by 3rd party tools. Defaults to the operating system username.
-v, --v Level number for the log level verbosity
--vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
2. 示例
- 停止与启动一个 node
查看 minikube 管理的集群已有的 node 列表
$ minikube-v1.18.1 -p k8s-v1.18.20 node list
k8s-v1.18.20 192.168.39.45
k8s-v1.18.20-m04 192.168.39.175
查看 k8s 集群中 node 列表的状态
$ kubectl get node
NAME STATUS ROLES AGE VERSION
k8s-v1.18.20 Ready master 18h v1.18.20
k8s-v1.18.20-m04 Ready <none> 22m v1.18.20
停止一个 node,类型关机
$ minikube-v1.18.1 -p k8s-v1.18.20 node stop k8s-v1.18.20-m04
✋ Stopping node "k8s-v1.18.20-m04" ...
🛑 Successfully stopped node k8s-v1.18.20-m04
node 停止后,在 k8s 集群中状态变成 NotReady
$ kubectl get node
NAME STATUS ROLES AGE VERSION
k8s-v1.18.20 Ready master 18h v1.18.20
k8s-v1.18.20-m04 NotReady <none> 24m v1.18.20
启动这个已经停止的 node
$ minikube-v1.18.1 -p k8s-v1.18.20 node start k8s-v1.18.20-m04
👍 Starting node k8s-v1.18.20-m04 in cluster k8s-v1.18.20
🔄 Restarting existing kvm2 VM for "k8s-v1.18.20-m04" ...
🐳 正在 Docker 20.10.3 中准备 Kubernetes v1.18.20…
🔎 Verifying Kubernetes components...
😄 Successfully started node k8s-v1.18.20-m04!
node 启动后节点状态变成 Ready
$ kubectl get node
NAME STATUS ROLES AGE VERSION
k8s-v1.18.20 Ready master 18h v1.18.20
k8s-v1.18.20-m04 Ready <none> 25m v1.18.20