cdc9770346
Automatic merge from submit-queue (batch tested with PRs 47403, 46646, 46906, 46527, 46792) Avoid redundant copying of tars during kube-up for gce if the same file already exists **What this PR does / why we need it**: Whenever I execute cluster/kube-up.sh it copies my tar files to google cloud, even if the files haven't changed. This PR checks to see whether the files already exist, and avoids uploading them again. These files are large and can take a long time to upload. **Which issue this PR fixes**: fixes #46791 **Special notes for your reviewer**: Here is the new output: cluster/kube-up.sh ... Starting cluster in us-central1-b using provider gce ... calling verify-prereqs ... calling verify-kube-binaries ... calling kube-up Project: PROJECT Zone: us-central1-b +++ Staging server tars to Google Storage: gs://kubernetes-staging-PROJECT/kubernetes-devel +++ kubernetes-server-linux-amd64.tar.gz uploaded earlier, cloud and local file md5 match (md5 = 3a095kcf27267a71fe58f91f89fab1bc) **Release note**: ```cluster/kube-up.sh on gce now avoids redundant copying of kubernetes tars if the local and cloud files' md5 hash match``` |
||
|---|---|---|
| .. | ||
| container-linux | ||
| debian | ||
| gci | ||
| BUILD | ||
| config-common.sh | ||
| config-default.sh | ||
| config-test.sh | ||
| configure-vm.sh | ||
| cos | ||
| delete-stranded-load-balancers.sh | ||
| list-resources.sh | ||
| OWNERS | ||
| ubuntu | ||
| upgrade.sh | ||
| util.sh | ||