Kubernetes Liveness Probe Logging

We’re using Kubernetes 1.1.3 with its default fluentd-elasticsearch logging.

We also use LivenessProbes on our containers to make sure they operate as expected.

  • How to export the docker variables?
  • Not able to install the gem “rmagick” with docker
  • Calabash android.util.AndroidException: INSTRUMENTATION_FAILED
  • Docker-machine resource limit
  • Docker Port forwarding doesn't call css and images
  • broken dockerfile : github deploy key no longer copied correctly
  • Our problem is that lines we send out to the STDOUT from the LivenessProbe does not appear to reach Elastic Search.

    Is there a way to make fluentd ship LivenessProbes output like it does to regular containers in a pod?

  • Getting docker pull to default pull from a private registry?
  • Phabricator git clone error 403
  • Access db as localhost from docker container
  • docker --volumes-from not mounting any files
  • Github repo with more than one python packages
  • How can I use docker for drupal?
  • One Solution collect form web for “Kubernetes Liveness Probe Logging”

    The output from the probe is swallowed by the Kubelet component on the node, which is responsible for running the probes (source code, if you’re interested). If a probe fails, its output will be recorded as an event associated with the pod, which should be accessible through the API.

    The output of successful probes isn’t recorded anywhere unless your Kubelet has a log level of at least –v=4, in which case it’ll be in the Kubelet’s logs.

    Feel free to file a feature request in a Github issue if you have ideas of what you’d like to be done with the output 🙂

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.