[kubernetes-users] Re: livenessProbe failed won't set pod status Ready=False

Sorry, my mistake, it seems that the ready=True is due to `initialDelaySeconds` has been set `30s`, and within the 30 seconds, the nginx POD would be `Ready`. BTW, `initialDelaySeconds` is likely to said `I'm not ready in this period, and it's ok, I need some time to warm up`, but POD status

[kubernetes-users] livenessProbe failed won't set pod status Ready=False

Hi team, I have been setup a nginx pod, and was confused about the healthcheck effect: 1. while readinessProbe failed, the nginx pod would be set Ready=False, but the POD didn't be killed; 2. while livenessProbe failed, the nginx pod would be killed, restartCount +1, and the Ready is always

Re: [kubernetes-users] Re: pod crashes when secuityContext used.

Thanks for the followup! On Fri, Feb 2, 2018 at 3:56 PM, R Melton wrote: > > I later went back and created a new image file (on docker) and reran the > runAsUser (and fsGroup) yaml file and it worked correctly. > > On Friday, February 2, 2018 at 11:52:07 AM UTC-6, R Melton

[kubernetes-users] Re: pod crashes when secuityContext used.

I later went back and created a new image file (on docker) and reran the runAsUser (and fsGroup) yaml file and it worked correctly. On Friday, February 2, 2018 at 11:52:07 AM UTC-6, R Melton wrote: > > using kubectl v1.9 on client and server. > ubuntu 16.04 server on GCP. > > I was trying to

Re: [kubernetes-users] Measuring disk latency on GKE

That worked great - thanks for the clue stick. On Friday, February 2, 2018 at 12:22:53 AM UTC-7, Ahmet Alp Balkan wrote: > > You can have CoreOS toolbox on GKE COS nodes: > https://cloud.google.com/container-optimized-os/docs/how-to/toolbox > > Just type "toolbox" when you SSH into the node. >

[kubernetes-users] Re: pod crashes when secuityContext used.

thanks for the help. the image comes from gcr.io so i posted a request on this image over there. On Friday, February 2, 2018 at 11:52:07 AM UTC-6, R Melton wrote: > > using kubectl v1.9 on client and server. > ubuntu 16.04 server on GCP. > > I was trying to follow the demo listed on >

Re: [kubernetes-users] pod crashes when secuityContext used.

It looks like that file is not readable by a non-root user. You're volunteering to lower your privileges, but you need to account for that in the image. If this is a custom image, chmod ugo+r that file? If it is a pre-built image, yell at whoever built it. On Fri, Feb 2, 2018 at 9:52 AM, R

[kubernetes-users] pod crashes when secuityContext used.

using kubectl v1.9 on client and server. ubuntu 16.04 server on GCP. I was trying to follow the demo listed on https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ which assigns a security context to a pod when it is created. Pod yaml file is: apiVersion: v1kind: