0

The output from a liveness probe failure when using exec does not show up in the kubelet event logs (kubernetes version 1.3.2).

For example, I created a pod from the liveness probe example here: http://kubernetes.io/docs/user-guide/liveness/

Using exec-liveness.yaml, I do not get any output from why the Liveness probe failed:

Events:
  FirstSeen LastSeen    Count   From                            SubobjectPath           TypeReason      Message
  --------- --------    -----   ----                            -------------           --------    ------      -------
  1m        1m      1   {default-scheduler }                                    Normal      Scheduled   Successfully assigned liveness-exec to my-node
  1m        1m      1   {kubelet my-node}   spec.containers{liveness}   Normal      Pulling     pulling image "gcr.io/google_containers/busybox"
  1m        1m      1   {kubelet my-node}   spec.containers{liveness}   Normal      Pulled      Successfully pulled image "gcr.io/google_containers/busybox"
  1m        1m      1   {kubelet my-node}   spec.containers{liveness}   Normal      Created     Created container with docker id e84949417706
  1m        1m      1   {kubelet my-node}   spec.containers{liveness}   Normal      Started     Started container with docker id e84949417706
  44s       24s     3   {kubelet my-node}   spec.containers{liveness}   Warning     Unhealthy   Liveness probe failed:
4

1 に答える 1

3

これは、 https://github.com/kubernetes/kubernetes/pull/30731によって Kubernetes v1.4 で修正されるバグです。

于 2016-08-30T17:51:34.773 に答える