title: Attempting to share cluster access results in creating new cluster
body: <p>I have deleted the config file I used when experimenting with Kubernetes on my AWS (using <a href="http://kubernetes.io/v1.0/docs/getting-started-guides/aws.html" rel="nofollow">this</a> tutorial) and replaced it with another devs config file when they set up Kubernetes on a shared AWS (using <a href="https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/user-guide/sharing-clusters.md" rel="nofollow">this</a>). When I run <code>kubectl config view</code> I see the following above the users section:</p>
  
  <pre><code>- cluster:
      certificate-authority-data: REDACTED
      server: &lt;removed&gt;
    name: aws_kubernetes
  contexts:
  - context:
      cluster: aws_kubernetes
      user: aws_kubernetes
    name: aws_kubernetes
  current-context: aws_kubernetes
  </code></pre>
  
  <p>This leads me to believe that my config should be pointing to use our shared AWS but whenever I run <code>cluster/kube-up.sh</code> it creates a new GCE cluster so I'm thinking I'm using the wrong command to spin up the cluster on AWS.</p>
  
  <p>Am I using the wrong command/missing a flag/etc? Additionally I'm thinking kube-up creates a new cluster instead of recreating a previously instantiated one.</p>