<p>I'm using K8S <code>1.14</code> and Helm <code>3.3.1</code>.</p>
<p>I have an app which <strong>works when deployed without probes</strong>. Then I set two trivial probes:</p>
<pre class="lang-yaml prettyprint-override"><code>          livenessProbe:
            exec:
              command:
                - ls
                - /mnt
            initialDelaySeconds: 5
            periodSeconds: 5

          readinessProbe:
            exec:
              command:
                - ls
                - /mnt
            initialDelaySeconds: 5
            periodSeconds: 5
</code></pre>
<p>When I deploy via <code>helm upgrade</code>, the command eventually (~5 mins) fails with:</p>
<pre><code>Error: UPGRADE FAILED: release my-app failed, and has been rolled back due to atomic being set: timed out waiting for the condition
</code></pre>
<p>But in the events log there is no trace of any probe:</p>
<pre><code>5m21s       Normal    ScalingReplicaSet         deployment/my-app     Scaled up replica set my-app-7 to 1
5m21s       Normal    Scheduled                 pod/my-app-7-6        Successfully assigned default/my-app-7-6 to gke-foo-testing-foo-testing-node-po-111-r0cu
5m21s       Normal    LoadBalancerNegNotReady   pod/my-app-7-6        Waiting for pod to become healthy in at least one of the NEG(s): [k8s1-222-default-my-app-80-54]
5m21s       Normal    SuccessfulCreate          replicaset/my-app-7   Created pod: my-app-7-6
5m20s       Normal    Pulling                   pod/my-app-7-6        Pulling image &quot;my-registry/my-app:v0.1&quot;
5m20s       Normal    Pulled                    pod/my-app-7-6        Successfully pulled image &quot;my-registry/my-app:v0.1&quot;
5m20s       Normal    Created                   pod/my-app-7-6        Created container my-app
5m20s       Normal    Started                   pod/my-app-7-6        Started container my-app
5m15s       Normal    Attach                    service/my-app        Attach 1 network endpoint(s) (NEG &quot;k8s1-222-default-my-app-80-54&quot; in zone &quot;europe-west3-a&quot;)
19s         Normal    ScalingReplicaSet         deployment/my-app     Scaled down replica set my-app-7 to 0
19s         Normal    SuccessfulDelete          replicaset/my-app-7   Deleted pod: my-app-7-6
19s         Normal    Killing                   pod/my-app-7-6        Stopping container my-app

</code></pre>
<p>Hence the question: what are the probes doing and where?</p>

<p>I reproduced the same scenario here and everything went fine. The release was deployed and the pod is running. Did you check within the container if the <code>/mnt</code> really exists?</p>
<pre><code>      Events:
      Type    Reason     Age    From               Message
      ----    ------     ----   ----               -------
      Normal  Scheduled  3m41s                     Successfully assigned default/nginx-deployment2-5cdd568667-blsc7 to minikube
      Normal  Pulling    3m41s  kubelet, minikube  Pulling image &quot;nginx&quot;
      Normal  Pulled     3m38s  kubelet, minikube  Successfully pulled image &quot;nginx&quot; in 2.769840982s
      Normal  Created    3m38s  kubelet, minikube  Created container nginx
      Normal  Started    3m38s  kubelet, minikube  Started container nginx


    NAME                                 READY   STATUS    RESTARTS   AGE
    nginx-deployment2-5cdd568667-blsc7   1/1     Running   0          4m59s
</code></pre>
<pre><code>    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: nginx-deployment2
    spec:
      selector:
        matchLabels:
          app: ameba
      replicas: 1
      template:
        metadata:
          labels:
            app: ameba
        spec:
          containers:
          - name: nginx
            image: nginx
            ports:
            - containerPort: 80
              name: nginx-port
            livenessProbe:
              exec:
                command:
                  - ls
                  - /mnt
              initialDelaySeconds: 5
              periodSeconds: 5
    
            readinessProbe:
              exec:
                command:
                  - ls
                  - /mnt
              initialDelaySeconds: 5
              periodSeconds: 5
</code></pre>
