Unless I'm mistaken, https://github.com/kubernetes/kubernetes/issues/17219 discusses the issue you're describing.
On Fri, Jun 24, 2016 at 8:05 PM, kant kodali <[email protected]> wrote: > Hi Guys, > > I understand that kube-up.sh will create a new VPC by default when you > launch the cluster if you don't set the VPC_ID environment variable. We > have an existing VPC that everyone in my company shares so I set the > existing environment variable VPC_ID and I brought up the cluster and I am > trying to bring down the cluster because I want to change the instance size > but I fear that kube-down which eventually calls cluster/aws/util.sh in my > case because I use (AWS) will actually delete my VPC. everyone in my > company will be effected if the existing VPC will be deleted so I certainly > don't want that to happen. > > Please respond. > Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "Containers at Google" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-containers. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
