Installation stuck if previous context already exists in the cluster

[olga-mir]

this project works with default kubeconfig file and predictable context and cluster names. If cluster/context already exist in this file, then it will be trying to connect to this API server resulting in errors like:

E1007 06:55:06.397379   40888 memcache.go:238] couldn't get current server API group list: Get "https://cluster-mgmt-apiserver-<REDACTED_ID>.<REDACTED_REGION>.elb.amazonaws.com:6443/api?timeout=32s": EOF

Possible solutions:

1. add random string to cluster and context
2. mandate use of separate kubeconfig

This would be much safer than assuming that user doesn't have these contexts outside of the scope of this project