--service-cluster-ip-range is a flag on kube-apiserver, so maybe try
ps aux | grep kube-apiserver
and then look for the flag.
On Tue, Jun 7, 2016 at 10:29 AM, kant kodali <[email protected]> wrote:
> Hi Tim,
>
> Thanks for the response. here is the output from my terminal. I dont even
> see the variable SERVICE_CLUSTER_IP_RANGE. I dont even know that I should
> pass. I was just using default setttings. what should the value for
> SERVICE_CLUSTER_IP_RANGE
> be set to? and how can i pass?
>
> kant@kant-virtual-machine:~/kubernetes/cluster/ubuntu$ ps auxw | grep
> kube-controller
>
> root 3730 0.0 0.0 71244 2264 pts/9 S+ May19 0:00 sudo -E
> /home/kant/kubernetes/_output/local/bin/linux/amd64/kube-controller-manager
> --v=3 --service-account-private-key-file=/tmp/kube-serviceaccount.key
> --root-ca-file=/var/run/kubernetes/apiserver.crt
> --enable-hostpath-provisioner=false --master=127.0.0.1:8080
>
> root 3734 0.2 0.4 68268 39900 pts/9 Sl+ May19 75:13
> /home/kant/kubernetes/_output/local/bin/linux/amd64/kube-controller-manager
> --v=3 --service-account-private-key-file=/tmp/kube-serviceaccount.key
> --root-ca-file=/var/run/kubernetes/apiserver.crt
> --enable-hostpath-provisioner=false --master=127.0.0.1:8080
> kant 58074 0.0 0.0 15952 2184 pts/30 S+ 10:19 0:00 grep
> --color=auto kube-controller
>
>
> kant@kant-virtual-machine:~/kubernetes/cluster/ubuntu$ ~/kubectl get
> pods,svc,rc --all-namespaces
> NAMESPACE NAME READY STATUS
> RESTARTS AGE
> default busybox 1/1 Running
> 30 2d
> default persistence-progression-chza8 2/2 Running 1
> 9d
> kube-system kube-dns-v14-2l9b2 3/3 Running 0
> 43s
> NAMESPACE NAME CLUSTER-IP EXTERNAL-IP
> PORT(S) AGE
> default kubernetes 10.0.0.1 <none>
> 443/TCP 36d
> NAMESPACE NAME DESIRED CURRENT
> AGE
> default persistence-progression 1 1
> 35d
> kube-system kube-dns-v14 1 1
> 43s
>
>
>
> when I go to kubernetes/cluster/ubuntu and run the following.
>
> kant@kant-virtual-machine:~/kubernetes/cluster/ubuntu$ sudo
> ./deployAddons.sh
> Creating kube-system namespace...
> namespace "kube-system" created
> The namespace 'kube-system' is successfully created.
>
> Deploying DNS on Kubernetes
> replicationcontroller "kube-dns-v14" created
> The Service "kube-dns" is invalid.
> spec.clusterIP: Invalid value: "127.0.0.1": provided IP is not in the
> valid range
>
>
>
>
>
> On Tue, Jun 7, 2016 at 10:07 AM, 'Tim Hockin' via Containers at Google <
> [email protected]> wrote:
>
>> ps auxw | grep kube-controller
>
>
>
> --
> 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.
