How do I stop the existing running cluster? I couldn't find that in the
docs.



On Tue, Jun 7, 2016 at 1:53 PM, Rodrigo Campos <[email protected]> wrote:

> Use the kube-up as described in the doc. There are several solutions for
> different cloud providers (that will integrate with them, the load
> balancer, docker registry, network, etc.)
>
> If you want local, you can use the same with vagrant provider.
>
>
> On Tuesday, June 7, 2016, kant kodali <[email protected]> wrote:
>
>> I brought the cluster up by running hack/local-up-cluster.sh (saw that in
>> the documentation). If this isn't the right way to bring up the cluster
>> could you please tell me how to bring down the existing cluster and start
>> the right way?
>>
>> Thanks!
>>
>> On Tue, Jun 7, 2016 at 12:42 PM, kant kodali <[email protected]> wrote:
>>
>>> Also here is what I got when I did the following but unsure how to set
>>> *--cluster-dns *as well?
>>>
>>>
>>> kant@kant-virtual-machine:~/kubernetes$ ps aux | grep kubelet
>>>
>>> root       3733  0.0  0.0  71244  2416 pts/9    S+   May19   0:00 sudo
>>> -E /home/kant/kubernetes/_output/local/bin/linux/amd64/kubelet --v=3
>>> --chaos-chance=0.0 --container-runtime=docker --rkt-path=
>>> --rkt-stage1-image= --hostname-override=127.0.0.1 --address=127.0.0.1
>>> --api-servers=127.0.0.1:8080 --cpu-cfs-quota=false --
>>> *cluster-dns=8.8.8.8* --port=10250
>>>
>>> root       3740  0.9  0.6 751688 51284 pts/9    Sl+  May19 257:08
>>> /home/kant/kubernetes/_output/local/bin/linux/amd64/kubelet --v=3
>>> --chaos-chance=0.0 --container-runtime=docker --rkt-path=
>>> --rkt-stage1-image= --hostname-override=127.0.0.1 --address=127.0.0.1
>>> --api-servers=127.0.0.1:8080 --cpu-cfs-quota=false
>>> *--cluster-dns=8.8.8.8* --port=10250
>>> kant      82359  0.0  0.0  15948  2224 pts/29   S+   12:40   0:00 grep
>>> --color=auto kubelet
>>>
>>>
>>> On Tue, Jun 7, 2016 at 12:38 PM, kant kodali <[email protected]> wrote:
>>>
>>>> Hi Cole,
>>>>
>>>> Thanks for the response. Could you please provide more pointers. I am
>>>> still very new and processing all the documentation. I dont see kube-dns
>>>> yaml anywhere in my directory structure. any specific file? do I need
>>>> to restart something after the change?
>>>>
>>>> When I do kubectl get nodes it says 127.0.0.1 RUNNING so should I set
>>>> my clusterIP to 127.0.0.1 since I am using local ubuntu on vmware fusion?
>>>>
>>>> Thanks!
>>>>
>>>> On Tue, Jun 7, 2016 at 12:23 PM, Cole Mickens <[email protected]>
>>>> wrote:
>>>>
>>>>> That would be the problem then. You need to set the clusterIP in the
>>>>> kube-dns yaml to fall within the --service-cluster-ip-range. Additionally,
>>>>> you'll want to ensure that the clusterIP you choose is the same IP that 
>>>>> you
>>>>> pass to kubelet in the --cluster-dns flag.
>>>>>
>>>>> On Tue, Jun 7, 2016 at 12:09 PM, kant kodali <[email protected]>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> kant@kant-virtual-machine:~/kubernetes/cluster/ubuntu$ ps aux | grep
>>>>>> kube-apiserver
>>>>>> root       3712  0.0  0.0  71244  2168 pts/9    S+   May19   0:00
>>>>>> sudo -E 
>>>>>> /home/kant/kubernetes/_output/local/bin/linux/amd64/kube-apiserver
>>>>>> --v=3 --cert-dir=/var/run/kubernetes
>>>>>> --service-account-key-file=/tmp/kube-serviceaccount.key
>>>>>> --service-account-lookup=false
>>>>>> --admission-control=NamespaceLifecycle,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota
>>>>>> --insecure-bind-address=127.0.0.1 --insecure-port=8080 --etcd-servers=
>>>>>> http://127.0.0.1:4001 *--service-cluster-ip-range=10.0.0.0/24
>>>>>> <http://10.0.0.0/24>* --cors-allowed-origins=/127.0.0.1
>>>>>> (:[0-9]+)?$,/localhost(:[0-9]+)?$
>>>>>>
>>>>>> root       3717  1.4  9.4 839508 774272 pts/9   Sl+  May19 388:49
>>>>>> /home/kant/kubernetes/_output/local/bin/linux/amd64/kube-apiserver --v=3
>>>>>> --cert-dir=/var/run/kubernetes
>>>>>> --service-account-key-file=/tmp/kube-serviceaccount.key
>>>>>> --service-account-lookup=false
>>>>>> --admission-control=NamespaceLifecycle,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota
>>>>>> --insecure-bind-address=127.0.0.1 --insecure-port=8080 --etcd-servers=
>>>>>> http://127.0.0.1:4001* --service-cluster-ip-range=10.0.0.0/24
>>>>>> <http://10.0.0.0/24>* --cors-allowed-origins=/127.0.0.1
>>>>>> (:[0-9]+)?$,/localhost(:[0-9]+)?$
>>>>>> kant      76526  0.0  0.0  15952  2224 pts/30   S+   12:06   0:00
>>>>>> grep --color=auto kube-apiserver
>>>>>>
>>>>>>
>>>>>> On Tue, Jun 7, 2016 at 12:01 PM, Cole Mickens <[email protected]
>>>>>> > wrote:
>>>>>>
>>>>>>>   ps aux | grep kube-apiserver
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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 a topic in the
>>>>> Google Groups "Containers at Google" group.
>>>>> To unsubscribe from this topic, visit
>>>>> https://groups.google.com/d/topic/google-containers/d7CBdPagD3E/unsubscribe
>>>>> .
>>>>> To unsubscribe from this group and all its topics, 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.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Containers at Google" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-containers/d7CBdPagD3E/unsubscribe
> .
> To unsubscribe from this group and all its topics, 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.

Reply via email to