Re: [kubernetes-users] error: the server doesn't have a resource type "cronjobs"
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 <ramsahay.si...@surmountsoft.com> Reply: Ram Sahay <ramsahay.si...@surmountsoft.com> Date: 6 April 2018 at 14:17:28 To: Michael Hausenblas <michael.hausenb...@gmail.com> Cc: kubernetes-users@googlegroups.com <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 > >> > > > > >> Subject: [kubernetes-users] error: the server doesn't have a resource > > > >> type "cronjobs" > > > >> > > > >> > Hi Everyone > > > >> > > > > >> > all ti
Re: [kubernetes-users] error: the server doesn't have a resource type "cronjobs"
> 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 <ramsahay.si...@surmountsoft.com> Reply: Ram Sahay <ramsahay.si...@surmountsoft.com> Date: 6 April 2018 at 13:59:17 To: Michael Hausenblas <michael.hausenb...@gmail.com> Cc: kubernetes-users@googlegroups.com <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 > >> > > >> 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" 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" 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"
What does the following command give you? kubectl version --short Cheers, Michael -- Michael Hausenblas Ireland, Europe http://mhausenblas.info/ -Original Message- From: Ram Sahay <ramsahay.si...@surmountsoft.com> Reply: kubernetes-users@googlegroups.com <kubernetes-users@googlegroups.com> Date: 6 April 2018 at 12:45:03 To: Kubernetes user discussion and Q <kubernetes-users@googlegroups.com> 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" 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" 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] How the communication happens in between pods
I suggest you peruse Mark’s excellent blog post (series) where in part 1 he answers your question and more in great detail: https://medium.com/google-cloud/understanding-kubernetes-networking-pods-7117dd28727 Cheers, Michael -- Michael Hausenblas Ireland, Europe http://mhausenblas.info/ -Original Message- From: rakesh_...@papajohns.com <rakesh_...@papajohns.com> Reply: kubernetes-users@googlegroups.com <kubernetes-users@googlegroups.com> Date: 7 February 2018 at 13:16:22 To: Kubernetes user discussion and Q <kubernetes-users@googlegroups.com> Subject: [kubernetes-users] How the communication happens in between pods > I have 4 pods in 4 different namespaces. Is communication between these ports > will happen > directly or should I do any changes to establish connection between them? > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes > user discussion and Q" 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" 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.
