Check for existing GCE resources in kube-up

[mwielgus]

Fix for #8285.
With this PR kube-up.sh will inform the user if he has some conflicting GCE resources (pds, templates, instances, etc) that should be removed. The check is made if:

• the user runs kube-up.sh in a terminal (stdout is bound to a terminal). In this case, if any resources are found, he will be asked for confirmation whether he wants to run kube-down or not.
• KUBE_UP_AUTOMATIC_CLEANUP is set to true. In this case kube-down is run automatically if needed.

[k8s-bot]

GCE e2e build/test passed for commit e13a3545bc97502dae17a7034e63e2eb3991bccb.

• Build Log
• Test Artifacts
• Internal Jenkins Results

[gmarek]

Please add a comment when this may give false negative.

[k8s-bot]

GCE e2e build/test passed for commit cbc55f29bf4f95b464cce3fbda714925ec7f3727.

• Build Log
• Test Artifacts
• Internal Jenkins Results

[gmarek]

LGTM. @zmerlynn are you OK with the current version?

[k8s-bot]

GCE e2e build/test passed for commit 66078be3bbc710e38001d4c7052a268ef99786e9.

• Build Log
• Test Artifacts
• Internal Jenkins Results

[k8s-bot]

GCE e2e build/test passed for commit 29a0c4bce90643270b49d45a4e05a2fd0b821d7b.

• Build Log
• Test Artifacts
• Internal Jenkins Results

[k8s-bot]

GCE e2e build/test passed for commit b33b881.

• Build Log
• Test Artifacts
• Internal Jenkins Results

[zmerlynn]

Have you tested this cross-project? I think the right way is to spin up a cluster in your main project and validate that none of the resources in that cluster block the cross-project creation.

[mwielgus]

Yes, it seems that with the added --project parameter everything works as intended.

./kube-up.sh
Starting cluster using provider: gce
... calling verify-prereqs

All components are up to date.

All components are up to date.

All components are up to date.
... calling kube-up
Project: my-other-project
Zone: us-central1-b
+++ Staging server tars to Google Storage: gs://kubernetes-staging-f1a4433947/devel
Looking for already existing resources
Starting master and configuring firewalls

No resources found.

[zmerlynn]

The current version LGTM.
On Jun 18, 2015 2:37 AM, "Marcin Wielgus" notifications@github.com wrote:

Yes, it seems that with the added --project parameter everything works as
intended.

./kube-up.sh
Starting cluster using provider: gce
... calling verify-prereqs

All components are up to date.

All components are up to date.

All components are up to date.
... calling kube-up
Project: my-other-project
Zone: us-central1-b
+++ Staging server tars to Google Storage: gs://kubernetes-staging-f1a4433947/devel
Looking for already existing resources
Starting master and configuring firewalls

No resources found.

—
Reply to this email directly or view it on GitHub
#9859 (comment)
.