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 <cole.mick...@gmail.com>
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 <kanth...@gmail.com> 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 <cole.mick...@gmail.com>
>> 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 google-containers+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-containers@googlegroups.com.
>> 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
> google-containers+unsubscr...@googlegroups.com.
> To post to this group, send email to google-containers@googlegroups.com.
> 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 google-containers+unsubscr...@googlegroups.com.
To post to this group, send email to google-containers@googlegroups.com.
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