Issue 1:
When I try to create a pod which mounts secret volumes I get a Unable to mount volumes for pod: exit status 1 error. For instance, when trying to create the example pod from https://github.com/kubernetes/kubernetes/tree/master/docs/user-guide/secrets :

$ curl -s https://raw.githubusercontent.com/kubernetes/kubernetes/master/docs/user-guide/secrets/secret.yaml | kubectl create -f -
secrets/test-secret
$ curl -s https://raw.githubusercontent.com/kubernetes/kubernetes/master/docs/user-guide/secrets/secret-pod.yaml | kubectl create -f -
pods/secret-test-pod
$ kubectl describe pod secret-test-pod
[...]
Events:
FirstSeen LastSeen Count From SubobjectPath Reason Message
Fri, 30 Oct 2015 10:56:30 +0000 Fri, 30 Oct 2015 10:56:30 +0000 1 {scheduler } scheduled Successfully assigned secret-test-pod to 127.0.0.1
Fri, 30 Oct 2015 10:56:30 +0000 Fri, 30 Oct 2015 11:31:37 +0000 211 {kubelet 127.0.0.1} failedMount Unable to mount volumes for pod "secret-test-pod_default": exit status 1
Fri, 30 Oct 2015 10:56:30 +0000 Fri, 30 Oct 2015 11:31:37 +0000 211 {kubelet 127.0.0.1} failedSync Error syncing pod, skipping: exit status 1

$ kubectl get secrets
NAME TYPE DATA
default-token-vjaxy kubernetes.io/service-account-token 2
test-secret Opaque 2

This is a single node containerized k8s cluster for local development (based on https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/docker.md ).

Here is how I specifically create the cluster and the definition of the master pod: https://gist.github.com/2opremio/12eafc0c2485d8d13f2a

I am running Docker version 1.8.2, build 0a8c2e3

Related to #16055 (I get a different error, though) and #8734 (but I do provide the --contenerized flag see https://gist.github.com/2opremio/12eafc0c2485d8d13f2a#file-create_cluster-sh-L27 ) and and somehow similar to openshift/origin#3072

Issue 2:
Resurrected from #66 and #761.

Probe currently supports the following control parameters:

// Length of time before health checking is activated. In seconds.
InitialDelaySeconds int64 `json:"initialDelaySeconds,omitempty" description:"number of seconds after the container has started before liveness probes are initiated; see http://releases.k8s.io/HEAD/docs/user-guide/pod-states.md#container-probes"`
// Length of time before health checking times out. In seconds.
TimeoutSeconds int64 `json:"timeoutSeconds,omitempty" description:"number of seconds after which liveness probes timeout; defaults to 1 second; see http://releases.k8s.io/HEAD/docs/user-guide/pod-states.md#container-probes"`

We should add the following common control parameters (matching, for instance, AppEngine's parameters and GCE's parameters):

// How often to probe
PeriodSeconds *int64
// Minimum consecutive successes for the probe to be considered successful after having reached the FailureThreshold; defaults to 1; must be 1 for liveness
SuccessThreshold *int
// Minimum consecutive failures for the probe to be considered failed; defaults to 1
FailureThreshold *int

At some point we'll probably want to add an enable/disable boolean, since it's convenient to be able to disable liveness probes without losing the parameter settings, but that's less critical than the above.