mirror of
https://github.com/kubernetes/kubernetes.git
synced 2026-05-16 10:59:36 -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. |
||
|---|---|---|
| .. | ||
| apiserver | ||
| client-go/ktesting | ||
| crd | ||
| fakedns | ||
| format | ||
| harness | ||
| hermeticpodcertificatesigner | ||
| image | ||
| junit | ||
| ktesting | ||
| kubeconfig | ||
| localupcluster | ||
| oidc | ||
| admission_webhook.go | ||
| audit.go | ||
| conditions.go | ||
| create_resources.go | ||
| delete_resources.go | ||
| density_utils.go | ||
| deployment.go | ||
| node.go | ||
| paths.go | ||
| pki_helpers.go | ||
| pod_store.go | ||
| replicaset.go | ||
| runners.go | ||
| tmpdir.go | ||
| update_resources.go | ||