Re: [kubernetes-users] error: the server doesn't have a resource type "cronjobs"

2018-04-07 Thread Ram Sahay
Hi

i am facing the problem in copy server to local please bellow path please
correct path ..
scp root@$MASTER_IP:/etc/kubernetes/admin.conf.

On Sat, Apr 7, 2018 at 11:52 PM, Ram Sahay 
wrote:

> Hi All
>
> i am facing the problem in copy server to local please bellow path.
> scp root@$MASTER_IP:/etc/kubernetes/admin.conf.
>
> On Fri, Apr 6, 2018 at 7:33 PM, Michael Hausenblas <
> michael.hausenb...@gmail.com> wrote:
>
>> OK, got it. Did you do the following as well?
>>
>>
>> sudo cp /etc/kubernetes/admin.conf $HOME/
>> sudo chown $(id -u):$(id -g) $HOME/admin.conf
>> export KUBECONFIG=$HOME/admin.conf
>>
>>
>>
>> Cheers,
>> Michael
>>
>> --
>> Michael Hausenblas
>> Ireland, Europe
>> http://mhausenblas.info/
>>
>> -Original Message-
>> From: Ram Sahay 
>> Reply: Ram Sahay 
>> Date: 6 April 2018 at 14:17:28
>> To: Michael Hausenblas 
>> Cc: kubernetes-users@googlegroups.com 
>> Subject:  Re: [kubernetes-users] error: the server doesn't have a
>> resource type "cronjobs"
>>
>> > 1-> Node not runing The connection to the server localhost:8080 was
>> refused
>> > - did you specify the right host or port?
>> > also command use in terminal run
>> > apt-get install -y kubelet kubeadm kubectl kubernetes-cni
>> >
>> > configure sucessfully.
>> >
>> > apt-get install -y kubelet kubeadm kubectl kubernetes-cni
>> > Reading package lists... Done
>> > Building dependency tree
>> > Reading state information... Done
>> > kubeadm is already the newest version (1.10.0-00).
>> > kubectl is already the newest version (1.10.0-00).
>> > kubelet is already the newest version (1.10.0-00).
>> > kubernetes-cni is already the newest version (0.6.0-00).
>> > 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
>> >
>> > please see
>> >
>> > 2-> Running
>> >
>> > Master is running ###
>> > kubectl --namespace=kube-system get all
>> > NAME READY STATUS RESTARTS
>> > AGE
>> > etcd-ip-172-31-29-248 1/1 Running 0
>> > 43m
>> > kube-apiserver-ip-172-31-29-248 1/1 Running 0
>> > 43m
>> > kube-controller-manager-ip-172-31-29-248 1/1 Running 0
>> > 43m
>> > kube-dns-86f4d74b45-rc2hn 0/3 Pending 0
>> > 44m
>> > kube-proxy-s7tnx 1/1 Running 0
>> > 44m
>> > kube-scheduler-ip-172-31-29-248 1/1 Running 0
>> > 43m
>> >
>> > NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
>> > kube-dns ClusterIP 10.96.0.10 53/UDP,53/TCP 44m
>> >
>> > NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE
>> > SELECTOR AGE
>> > kube-proxy 1 1 1 1 1
>> > 44m
>> >
>> > NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
>> > kube-dns 1 1 1 0 44m
>> >
>> > NAME DESIRED CURRENT READY AGE
>> > kube-dns-86f4d74b45 1 1 0 44m
>> >
>> >
>> > On Fri, Apr 6, 2018 at 6:41 PM, Michael Hausenblas <
>> > michael.hausenb...@gmail.com> wrote:
>> >
>> > > > The connection to the server localhost:8080 was refused - did you
>> specify
>> > > > the right host or port?
>> > >
>> > > This means kubectl is not correctly configured. Try with kubectl
>> > > --server=THE_IP_OF_YOUR_MASTER:8080 … and/or check your
>> configuration.
>> > >
>> > > Also, how did you provision your cluster? Using kubeadm maybe?
>> > >
>> > >
>> > > Cheers,
>> > > Michael
>> > >
>> > > --
>> > > Michael Hausenblas
>> > > Ireland, Europe
>> > > http://mhausenblas.info/
>> > >
>> > > -Original Message-
>> > > From: Ram Sahay
>> > > Reply: Ram Sahay
>> > > Date: 6 April 2018 at 13:59:17
>> > > To: Michael Hausenblas
>> > > Cc: kubernetes-users@googlegroups.com
>> > > Subject: Re: [kubernetes-users] error: the server doesn't have a
>> > > resource type "cronjobs"
>> > >
>> > > > Client Version: v1.10.0
>> > > > The connection to the server localhost:8080 was refused - did you
>> specify
>> > > > the right host or port?
>> > > >
>> > > > On Fri, Apr 6, 2018 at 6:28 PM, Ram Sahay
>> > > > wro

Re: [kubernetes-users] error: the server doesn't have a resource type "cronjobs"

2018-04-07 Thread Ram Sahay
Hi All

i am facing the problem in copy server to local please bellow path.
scp root@$MASTER_IP:/etc/kubernetes/admin.conf.

On Fri, Apr 6, 2018 at 7:33 PM, Michael Hausenblas <
michael.hausenb...@gmail.com> wrote:

> OK, got it. Did you do the following as well?
>
>
> sudo cp /etc/kubernetes/admin.conf $HOME/
> sudo chown $(id -u):$(id -g) $HOME/admin.conf
> export KUBECONFIG=$HOME/admin.conf
>
>
>
> Cheers,
> Michael
>
> --
> Michael Hausenblas
> Ireland, Europe
> http://mhausenblas.info/
>
> -Original Message-
> From: Ram Sahay 
> Reply: Ram Sahay 
> Date: 6 April 2018 at 14:17:28
> To: Michael Hausenblas 
> Cc: kubernetes-users@googlegroups.com 
> Subject:  Re: [kubernetes-users] error: the server doesn't have a
> resource type "cronjobs"
>
> > 1-> Node not runing The connection to the server localhost:8080 was
> refused
> > - did you specify the right host or port?
> > also command use in terminal run
> > apt-get install -y kubelet kubeadm kubectl kubernetes-cni
> >
> > configure sucessfully.
> >
> > apt-get install -y kubelet kubeadm kubectl kubernetes-cni
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > kubeadm is already the newest version (1.10.0-00).
> > kubectl is already the newest version (1.10.0-00).
> > kubelet is already the newest version (1.10.0-00).
> > kubernetes-cni is already the newest version (0.6.0-00).
> > 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
> >
> > please see
> >
> > 2-> Running
> >
> > Master is running ###
> > kubectl --namespace=kube-system get all
> > NAME READY STATUS RESTARTS
> > AGE
> > etcd-ip-172-31-29-248 1/1 Running 0
> > 43m
> > kube-apiserver-ip-172-31-29-248 1/1 Running 0
> > 43m
> > kube-controller-manager-ip-172-31-29-248 1/1 Running 0
> > 43m
> > kube-dns-86f4d74b45-rc2hn 0/3 Pending 0
> > 44m
> > kube-proxy-s7tnx 1/1 Running 0
> > 44m
> > kube-scheduler-ip-172-31-29-248 1/1 Running 0
> > 43m
> >
> > NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
> > kube-dns ClusterIP 10.96.0.10 53/UDP,53/TCP 44m
> >
> > NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE
> > SELECTOR AGE
> > kube-proxy 1 1 1 1 1
> > 44m
> >
> > NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
> > kube-dns 1 1 1 0 44m
> >
> > NAME DESIRED CURRENT READY AGE
> > kube-dns-86f4d74b45 1 1 0 44m
> >
> >
> > On Fri, Apr 6, 2018 at 6:41 PM, Michael Hausenblas <
> > michael.hausenb...@gmail.com> wrote:
> >
> > > > The connection to the server localhost:8080 was refused - did you
> specify
> > > > the right host or port?
> > >
> > > This means kubectl is not correctly configured. Try with kubectl
> > > --server=THE_IP_OF_YOUR_MASTER:8080 … and/or check your configuration.
> > >
> > > Also, how did you provision your cluster? Using kubeadm maybe?
> > >
> > >
> > > Cheers,
> > > Michael
> > >
> > > --
> > > Michael Hausenblas
> > > Ireland, Europe
> > > http://mhausenblas.info/
> > >
> > > -Original Message-
> > > From: Ram Sahay
> > > Reply: Ram Sahay
> > > Date: 6 April 2018 at 13:59:17
> > > To: Michael Hausenblas
> > > Cc: kubernetes-users@googlegroups.com
> > > Subject: Re: [kubernetes-users] error: the server doesn't have a
> > > resource type "cronjobs"
> > >
> > > > Client Version: v1.10.0
> > > > The connection to the server localhost:8080 was refused - did you
> specify
> > > > the right host or port?
> > > >
> > > > On Fri, Apr 6, 2018 at 6:28 PM, Ram Sahay
> > > > wrote:
> > > >
> > > > > Client Version: v1.10.0
> > > > > The connection to the server localhost:8080 was refused - did you
> > > specify
> > > > > the right host or port?
> > > > >
> > > > > On Fri, Apr 6, 2018 at 5:21 PM, Michael Hausenblas <
> > > > > michael.hausenb...@gmail.com> wrote:
> > > > >
> > > > >> What does the following command give you?
> > > > >>
> > > > >> kubectl version --short
> > > > >>
> > > > >> Cheers,
> > > > >> Michael
> > > > >>
> > > > >>

Re: [kubernetes-users] error: the server doesn't have a resource type "cronjobs"

2018-04-06 Thread Michael Hausenblas
OK, got it. Did you do the following as well?


sudo cp /etc/kubernetes/admin.conf $HOME/
sudo chown $(id -u):$(id -g) $HOME/admin.conf
export KUBECONFIG=$HOME/admin.conf



Cheers,
Michael

--
Michael Hausenblas
Ireland, Europe
http://mhausenblas.info/

-Original Message-
From: Ram Sahay 
Reply: Ram Sahay 
Date: 6 April 2018 at 14:17:28
To: Michael Hausenblas 
Cc: kubernetes-users@googlegroups.com 
Subject:  Re: [kubernetes-users] error: the server doesn't have a
resource type "cronjobs"

> 1-> Node not runing The connection to the server localhost:8080 was refused
> - did you specify the right host or port?
> also command use in terminal run
> apt-get install -y kubelet kubeadm kubectl kubernetes-cni
>
> configure sucessfully.
>
> apt-get install -y kubelet kubeadm kubectl kubernetes-cni
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> kubeadm is already the newest version (1.10.0-00).
> kubectl is already the newest version (1.10.0-00).
> kubelet is already the newest version (1.10.0-00).
> kubernetes-cni is already the newest version (0.6.0-00).
> 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
>
> please see
>
> 2-> Running
>
> Master is running ###
> kubectl --namespace=kube-system get all
> NAME READY STATUS RESTARTS
> AGE
> etcd-ip-172-31-29-248 1/1 Running 0
> 43m
> kube-apiserver-ip-172-31-29-248 1/1 Running 0
> 43m
> kube-controller-manager-ip-172-31-29-248 1/1 Running 0
> 43m
> kube-dns-86f4d74b45-rc2hn 0/3 Pending 0
> 44m
> kube-proxy-s7tnx 1/1 Running 0
> 44m
> kube-scheduler-ip-172-31-29-248 1/1 Running 0
> 43m
>
> NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
> kube-dns ClusterIP 10.96.0.10 53/UDP,53/TCP 44m
>
> NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE
> SELECTOR AGE
> kube-proxy 1 1 1 1 1
> 44m
>
> NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
> kube-dns 1 1 1 0 44m
>
> NAME DESIRED CURRENT READY AGE
> kube-dns-86f4d74b45 1 1 0 44m
>
>
> On Fri, Apr 6, 2018 at 6:41 PM, Michael Hausenblas <
> michael.hausenb...@gmail.com> wrote:
>
> > > The connection to the server localhost:8080 was refused - did you specify
> > > the right host or port?
> >
> > This means kubectl is not correctly configured. Try with kubectl
> > --server=THE_IP_OF_YOUR_MASTER:8080 … and/or check your configuration.
> >
> > Also, how did you provision your cluster? Using kubeadm maybe?
> >
> >
> > Cheers,
> > Michael
> >
> > --
> > Michael Hausenblas
> > Ireland, Europe
> > http://mhausenblas.info/
> >
> > -Original Message-
> > From: Ram Sahay
> > Reply: Ram Sahay
> > Date: 6 April 2018 at 13:59:17
> > To: Michael Hausenblas
> > Cc: kubernetes-users@googlegroups.com
> > Subject: Re: [kubernetes-users] error: the server doesn't have a
> > resource type "cronjobs"
> >
> > > Client Version: v1.10.0
> > > The connection to the server localhost:8080 was refused - did you specify
> > > the right host or port?
> > >
> > > On Fri, Apr 6, 2018 at 6:28 PM, Ram Sahay
> > > wrote:
> > >
> > > > Client Version: v1.10.0
> > > > The connection to the server localhost:8080 was refused - did you
> > specify
> > > > the right host or port?
> > > >
> > > > On Fri, Apr 6, 2018 at 5:21 PM, Michael Hausenblas <
> > > > michael.hausenb...@gmail.com> wrote:
> > > >
> > > >> What does the following command give you?
> > > >>
> > > >> kubectl version --short
> > > >>
> > > >> Cheers,
> > > >> Michael
> > > >>
> > > >> --
> > > >> Michael Hausenblas
> > > >> Ireland, Europe
> > > >> http://mhausenblas.info/
> > > >>
> > > >> -Original Message-
> > > >> From: Ram Sahay
> > > >> Reply: kubernetes-users@googlegroups.com > >> .com>
> > > >> Date: 6 April 2018 at 12:45:03
> > > >> To: Kubernetes user discussion and Q&A > >> >
> > > >> Subject: [kubernetes-users] error: the server doesn't have a resource
> > > >> type "cronjobs"
> > > >>
> > > >> > Hi Everyone
> > > >> >
> > > >> > all time face problem in terminal close than error: the server
> > doesn't
> > > >> > have a resource type "cr

Re: [kubernetes-users] error: the server doesn't have a resource type "cronjobs"

2018-04-06 Thread Ram Sahay
1-> Node not runing The connection to the server localhost:8080 was refused
- did you specify the right host or port?
 also command use in terminal run
apt-get install -y kubelet kubeadm kubectl kubernetes-cni

configure sucessfully.

 apt-get install -y kubelet kubeadm kubectl kubernetes-cni
Reading package lists... Done
Building dependency tree
Reading state information... Done
kubeadm is already the newest version (1.10.0-00).
kubectl is already the newest version (1.10.0-00).
kubelet is already the newest version (1.10.0-00).
kubernetes-cni is already the newest version (0.6.0-00).
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

please see

2-> Running

Master is running ###
 kubectl --namespace=kube-system get all
NAME   READY STATUSRESTARTS
AGE
etcd-ip-172-31-29-248  1/1   Running   0
43m
kube-apiserver-ip-172-31-29-2481/1   Running   0
43m
kube-controller-manager-ip-172-31-29-248   1/1   Running   0
43m
kube-dns-86f4d74b45-rc2hn  0/3   Pending   0
44m
kube-proxy-s7tnx   1/1   Running   0
44m
kube-scheduler-ip-172-31-29-2481/1   Running   0
43m

NAME   TYPECLUSTER-IP   EXTERNAL-IP   PORT(S) AGE
kube-dns   ClusterIP   10.96.0.10   53/UDP,53/TCP   44m

NAME DESIRED   CURRENT   READY UP-TO-DATE   AVAILABLE   NODE
SELECTOR   AGE
kube-proxy   1 1 1 11
  44m

NAME   DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
kube-dns   1 1 10   44m

NAME  DESIRED   CURRENT   READY AGE
kube-dns-86f4d74b45   1 1 0 44m


On Fri, Apr 6, 2018 at 6:41 PM, Michael Hausenblas <
michael.hausenb...@gmail.com> wrote:

> > The connection to the server localhost:8080 was refused - did you specify
> > the right host or port?
>
> This means kubectl is not correctly configured. Try with kubectl
> --server=THE_IP_OF_YOUR_MASTER:8080 … and/or check your configuration.
>
> Also, how did you provision your cluster? Using kubeadm maybe?
>
>
> Cheers,
> Michael
>
> --
> Michael Hausenblas
> Ireland, Europe
> http://mhausenblas.info/
>
> -Original Message-
> From: Ram Sahay 
> Reply: Ram Sahay 
> Date: 6 April 2018 at 13:59:17
> To: Michael Hausenblas 
> Cc: kubernetes-users@googlegroups.com 
> Subject:  Re: [kubernetes-users] error: the server doesn't have a
> resource type "cronjobs"
>
> > Client Version: v1.10.0
> > The connection to the server localhost:8080 was refused - did you specify
> > the right host or port?
> >
> > On Fri, Apr 6, 2018 at 6:28 PM, Ram Sahay
> > wrote:
> >
> > > Client Version: v1.10.0
> > > The connection to the server localhost:8080 was refused - did you
> specify
> > > the right host or port?
> > >
> > > On Fri, Apr 6, 2018 at 5:21 PM, Michael Hausenblas <
> > > michael.hausenb...@gmail.com> wrote:
> > >
> > >> What does the following command give you?
> > >>
> > >> kubectl version --short
> > >>
> > >> Cheers,
> > >> Michael
> > >>
> > >> --
> > >> Michael Hausenblas
> > >> Ireland, Europe
> > >> http://mhausenblas.info/
> > >>
> > >> -Original Message-
> > >> From: Ram Sahay
> > >> Reply: kubernetes-users@googlegroups.com > >> .com>
> > >> Date: 6 April 2018 at 12:45:03
> > >> To: Kubernetes user discussion and Q&A > >> >
> > >> Subject: [kubernetes-users] error: the server doesn't have a resource
> > >> type "cronjobs"
> > >>
> > >> > Hi Everyone
> > >> >
> > >> > all time face problem in terminal close than error: the server
> doesn't
> > >> > have a resource type "cronjobs"
> > >> > how to fix proble .
> > >> >
> > >> > --
> > >> > You received this message because you are subscribed to the Google
> > >> Groups "Kubernetes
> > >> > user discussion and Q&A" group.
> > >> > To unsubscribe from this group and stop receiving emails from it,
> send
> > >> an email to kubernetes-users+unsubscr...@googlegroups.com.
> > >> > To post to this group, send email to kubernetes-users@googlegroups.
> com.
> > >> > Visit this group at https://groups.google.com/
> group/kubernetes-users.
> > >> > For more options, visit https://groups.google.com/d/optout.
> > >> >
> > >>
> > >
> > >
> >
>

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.


Re: [kubernetes-users] error: the server doesn't have a resource type "cronjobs"

2018-04-06 Thread Michael Hausenblas
> The connection to the server localhost:8080 was refused - did you specify
> the right host or port?

This means kubectl is not correctly configured. Try with kubectl
--server=THE_IP_OF_YOUR_MASTER:8080 … and/or check your configuration.

Also, how did you provision your cluster? Using kubeadm maybe?


Cheers,
Michael

--
Michael Hausenblas
Ireland, Europe
http://mhausenblas.info/

-Original Message-
From: Ram Sahay 
Reply: Ram Sahay 
Date: 6 April 2018 at 13:59:17
To: Michael Hausenblas 
Cc: kubernetes-users@googlegroups.com 
Subject:  Re: [kubernetes-users] error: the server doesn't have a
resource type "cronjobs"

> Client Version: v1.10.0
> The connection to the server localhost:8080 was refused - did you specify
> the right host or port?
>
> On Fri, Apr 6, 2018 at 6:28 PM, Ram Sahay
> wrote:
>
> > Client Version: v1.10.0
> > The connection to the server localhost:8080 was refused - did you specify
> > the right host or port?
> >
> > On Fri, Apr 6, 2018 at 5:21 PM, Michael Hausenblas <
> > michael.hausenb...@gmail.com> wrote:
> >
> >> What does the following command give you?
> >>
> >> kubectl version --short
> >>
> >> Cheers,
> >> Michael
> >>
> >> --
> >> Michael Hausenblas
> >> Ireland, Europe
> >> http://mhausenblas.info/
> >>
> >> -Original Message-
> >> From: Ram Sahay
> >> Reply: kubernetes-users@googlegroups.com > >> .com>
> >> Date: 6 April 2018 at 12:45:03
> >> To: Kubernetes user discussion and Q&A > >> >
> >> Subject: [kubernetes-users] error: the server doesn't have a resource
> >> type "cronjobs"
> >>
> >> > Hi Everyone
> >> >
> >> > all time face problem in terminal close than error: the server doesn't
> >> > have a resource type "cronjobs"
> >> > how to fix proble .
> >> >
> >> > --
> >> > You received this message because you are subscribed to the Google
> >> Groups "Kubernetes
> >> > user discussion and Q&A" group.
> >> > To unsubscribe from this group and stop receiving emails from it, send
> >> an email to kubernetes-users+unsubscr...@googlegroups.com.
> >> > To post to this group, send email to kubernetes-users@googlegroups.com.
> >> > Visit this group at https://groups.google.com/group/kubernetes-users.
> >> > For more options, visit https://groups.google.com/d/optout.
> >> >
> >>
> >
> >
>

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.


Re: [kubernetes-users] error: the server doesn't have a resource type "cronjobs"

2018-04-06 Thread Ram Sahay
Client Version: v1.10.0
The connection to the server localhost:8080 was refused - did you specify
the right host or port?

On Fri, Apr 6, 2018 at 5:21 PM, Michael Hausenblas <
michael.hausenb...@gmail.com> wrote:

> What does the following command give you?
>
> kubectl version --short
>
> Cheers,
> Michael
>
> --
> Michael Hausenblas
> Ireland, Europe
> http://mhausenblas.info/
>
> -Original Message-
> From: Ram Sahay 
> Reply: kubernetes-users@googlegroups.com  googlegroups.com>
> Date: 6 April 2018 at 12:45:03
> To: Kubernetes user discussion and Q&A 
> Subject:  [kubernetes-users] error: the server doesn't have a resource
> type "cronjobs"
>
> > Hi Everyone
> >
> > all time face problem in terminal close than error: the server doesn't
> > have a resource type "cronjobs"
> > how to fix proble .
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Kubernetes
> > user discussion and Q&A" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to kubernetes-users+unsubscr...@googlegroups.com.
> > To post to this group, send email to kubernetes-users@googlegroups.com.
> > Visit this group at https://groups.google.com/group/kubernetes-users.
> > For more options, visit https://groups.google.com/d/optout.
> >
>

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.


Re: [kubernetes-users] error: the server doesn't have a resource type "cronjobs"

2018-04-06 Thread Ram Sahay
Client Version: v1.10.0
The connection to the server localhost:8080 was refused - did you specify
the right host or port?

On Fri, Apr 6, 2018 at 6:28 PM, Ram Sahay 
wrote:

> Client Version: v1.10.0
> The connection to the server localhost:8080 was refused - did you specify
> the right host or port?
>
> On Fri, Apr 6, 2018 at 5:21 PM, Michael Hausenblas <
> michael.hausenb...@gmail.com> wrote:
>
>> What does the following command give you?
>>
>> kubectl version --short
>>
>> Cheers,
>> Michael
>>
>> --
>> Michael Hausenblas
>> Ireland, Europe
>> http://mhausenblas.info/
>>
>> -Original Message-
>> From: Ram Sahay 
>> Reply: kubernetes-users@googlegroups.com > .com>
>> Date: 6 April 2018 at 12:45:03
>> To: Kubernetes user discussion and Q&A > >
>> Subject:  [kubernetes-users] error: the server doesn't have a resource
>> type "cronjobs"
>>
>> > Hi Everyone
>> >
>> > all time face problem in terminal close than error: the server doesn't
>> > have a resource type "cronjobs"
>> > how to fix proble .
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "Kubernetes
>> > user discussion and Q&A" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an email to kubernetes-users+unsubscr...@googlegroups.com.
>> > To post to this group, send email to kubernetes-users@googlegroups.com.
>> > Visit this group at https://groups.google.com/group/kubernetes-users.
>> > For more options, visit https://groups.google.com/d/optout.
>> >
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.


Re: [kubernetes-users] error: the server doesn't have a resource type "cronjobs"

2018-04-06 Thread Michael Hausenblas
What does the following command give you?

kubectl version --short

Cheers,
Michael

--
Michael Hausenblas
Ireland, Europe
http://mhausenblas.info/

-Original Message-
From: Ram Sahay 
Reply: kubernetes-users@googlegroups.com 
Date: 6 April 2018 at 12:45:03
To: Kubernetes user discussion and Q&A 
Subject:  [kubernetes-users] error: the server doesn't have a resource
type "cronjobs"

> Hi Everyone
>
> all time face problem in terminal close than error: the server doesn't
> have a resource type "cronjobs"
> how to fix proble .
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Kubernetes
> user discussion and Q&A" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.