mirror of
https://github.com/kubernetes/kubernetes.git
synced 2026-05-15 02:19:31 -04:00
a2b0ea30b0
The local-up-cluster.sh script was used as proxy for controlling the etcd lifecycle because the script was using a helper function that didn't support dry-run mode. That approach was flawed in several ways, causing etcd to be left running: - Cmd.Stop wasn't actually called for the script by Cluster.Stop. - If it had been called, the additional output during shutdown wouldn't have been processed, which might have caused the command to block instead of terminating (untested). - It's unclear whether the script would have handled the signal properly. A cleaner approach is to enable dry-run mode also in etcd .sh and then let Cluster manage it like any other long-running process. Then we can let local-up-cluster.sh terminate when it's done with its work. Cluster.Start can check it's result immediately. |
||
|---|---|---|
| .. | ||
| .gitattributes | ||
| etcd.sh | ||
| golang.sh | ||
| init.sh | ||
| logging.sh | ||
| protoc.sh | ||
| test.sh | ||
| util.sh | ||
| verify-generated.sh | ||
| version.sh | ||