The reason I was looking for it was that the health check for my pod didn't 
seem to be configuring the associated HTTP Health Check in GCE (it was 
picking up the default health check settings pointing to '/'). Turns out 
the issue was that I'd misread the GCE ingress instructions 
<https://github.com/kubernetes/contrib/blob/master/ingress/controllers/gce/README.md#health-checks>,
 
and was using a liveness probe instead of a readiness probe. Once I added 
the latter, everything worked correctly.

Thanks!

On Thursday, July 14, 2016 at 1:11:07 AM UTC-4, Robert Bailey wrote:
>
> There isn't a way for you to read logs from system pods running on the 
> master in GKE. Ideally, any critical logging statements would be exported 
> into the cluster as events that you could discover running `kubectl get 
> events` or even `kubectl describe ingress` on the Ingress object that isn't 
> working. 
>
> Why are you looking for that particular log statement?
>
> On Wed, Jul 13, 2016 at 9:20 PM, Michael Strickland <
> [email protected] <javascript:>> wrote:
>
>> Hello,
>>
>> I'm running a GKE cluster on k8s 1.3.0, and according to the Google Load 
>> Balancer Controller docs 
>> <https://github.com/kubernetes/contrib/blob/master/ingress/controllers/gce/BETA_LIMITATIONS.md>
>>  
>> it appears that one change since 1.2.5 is that:
>>
>> As of Kubernetes 1.3, GLBC runs as a static pod on the master.
>>>
>>
>> Which is great! One issue I'm running into however is in reading the logs 
>> from that pod, since best I can tell logs from the master node aren't 
>> exported to Stackdriver Logging.
>>
>> Is there currently any way to view those logs? Specifically, I'm trying 
>> to read the logging statements from this function 
>> <https://github.com/kubernetes/contrib/blob/0.7.0/ingress/controllers/gce/controller/utils.go#L424>
>> .
>>
>> Thanks!
>> Michael
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Containers at Google" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/google-containers.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Containers at Google" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-containers.
For more options, visit https://groups.google.com/d/optout.

Reply via email to