kubectl can't connect to cluster after creating daemonset that logs too much

[justin...@gmail.com]

Hi all,
I just created a daemonset on one of my Kubernetes clusters which is just a busybox logging to stdout. Unfortunately I think it is logging too much and I now can't connect to the cluster using kubectl. When I run a command I get this error "Error from server: client: etcd cluster is unavailable or misconfigured". Any help would be greatly appreciated.
Justin

[Brandon Philips]

Can you get logs from etcd to figure out what is wrong?

--
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-use...@googlegroups.com.
To post to this group, send email to kubernet...@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

[Justin Seely]

I managed to fix it by logging onto the master to use kubectl to delete the daemon set. Thanks for the response though Brandon.

You received this message because you are subscribed to a topic in the Google Groups "Kubernetes user discussion and Q&A" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kubernetes-users/r0naIJqrm5E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kubernetes-use...@googlegroups.com.

[Vishnu Kannan]

This is one of the reasons why the master node should ideally not be running user pods. 

We are working on making the system resilient to abusive pods. 

On Wed, Mar 22, 2017 at 3:04 PM, Justin Seely <justin...@gmail.com> wrote:

I managed to fix it by logging onto the master to use kubectl to delete the daemon set. Thanks for the response though Brandon.

On Wed, Mar 22, 2017 at 1:06 PM Brandon Philips <brandon...@coreos.com> wrote:

Can you get logs from etcd to figure out what is wrong?

On Wed, Mar 22, 2017 at 11:15 AM <justin...@gmail.com> wrote:

Hi all,
I just created a daemonset on one of my Kubernetes clusters which is just a busybox logging to stdout. Unfortunately I think it is logging too much and I now can't connect to the cluster using kubectl. When I run a command I get this error "Error from server: client: etcd cluster is unavailable or misconfigured". Any help would be greatly appreciated.
Justin

--

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+unsubscribe@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 a topic in the Google Groups "Kubernetes user discussion and Q&A" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kubernetes-users/r0naIJqrm5E/unsubscribe.

To unsubscribe from this group and all its topics, send an email to kubernetes-users+unsubscribe@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+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.