Re: [kubernetes-users] destoryed pod containers trigger

> kubectl logs ... --previous ? > I have tried that, but it shows `Error from server (BadRequest): previous terminated container "main" in pod "demo-1050-5fb5698d4f-8qtsw" not found` BTW, I found `maximum-dead-containers-per-container` and `maximum-dead-containers` to configure the policy,

Re: [kubernetes-users] Can you route external traffic to a pod without using a Google Cloud Loadbalancer or routing directly to the Node?

On Jan 31, 2018 12:03 PM, wrote: Hi guys, I was wondering if there is another way to route external traffic to a Pod. So I know that you can use a Kubernetes Service of type "LoadBalancer" which on GKE will automatically create a Google Cloud Loadbalancer for you (as

[kubernetes-users] Can you route external traffic to a pod without using a Google Cloud Loadbalancer or routing directly to the Node?

Hi guys, I was wondering if there is another way to route external traffic to a Pod. So I know that you can use a Kubernetes Service of type "LoadBalancer" which on GKE will automatically create a Google Cloud Loadbalancer for you (as described here

Re: [kubernetes-users] destoryed pod containers trigger

kubectl logs ... --previous ? On Wed, Jan 31, 2018 at 6:38 AM, Colstuwjx wrote: >> >> >>> >>> But, what if we want to trigger the detail exited reason for the exited >>> containers? Is there any parameters configure that? >> >> >> Have you checked the terminationGracePeriod?

Re: [kubernetes-users] destoryed pod containers trigger

On Wed, Jan 31, 2018 at 06:38:36AM -0800, Colstuwjx wrote: > > > >> But, what if we want to trigger the detail exited reason for the exited > >> containers? Is there any parameters configure that? > > > > Have you checked the terminationGracePeriod? I think it will do just that. > > I'm afraid

Re: [kubernetes-users] destoryed pod containers trigger

> > > > >> But, what if we want to trigger the detail exited reason for the exited >> containers? Is there any parameters configure that? >> > > Have you checked the terminationGracePeriod? I think it will do just that. > I'm afraid not, I need to check the exited container, such as some

[kubernetes-users] Re: Give me normal container name plz!

Oops pardon. This is solved by grouping and filtering -- 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

Re: [kubernetes-users] destoryed pod containers trigger

On Wednesday, January 31, 2018, Colstuwjx wrote: > Hi team, > > As I known, kubernetes will kill the POD while the readiness probe failed > over than `FailureThreshold` limit, and the unhealthy containers will be > deleted by kubelet. > I think only the liveness probe will

[kubernetes-users] Give me normal container name plz!

Hello! I

[kubernetes-users] destoryed pod containers trigger

Hi team, As I known, kubernetes will kill the POD while the readiness probe failed over than `FailureThreshold` limit, and the unhealthy containers will be deleted by kubelet. But, what if we want to trigger the detail exited reason for the exited containers? Is there any parameters configure

[kubernetes-users] kubeadm init fails on vmware vm

Hi, I'm trying to install kubernetes on a vmware vm which in theory should be pretty easy. I have done several test installs using qemu and virtualbox and both of those works perfectly using this guide: https://blog.alexellis.io/kubernetes-in-10-minutes/ (The only difference is that I'm