title: Waiting for pods: apiserver get stuck
body: <p>I am trying to implement auditing policy
  My yaml</p>
  
  <pre><code>~/.minikube/addons$ cat audit-policy.yaml 
  # Log all requests at the Metadata level.
  apiVersion: audit.k8s.io/v1beta1
  kind: Policy
  rules:
  - level: Metadata
  </code></pre>
  
  <p>Pods got stuck</p>
  
  <pre><code>minikube start  --extra-config=apiserver.Authorization.Mode=RBAC --extra-config=apiserver.Audit.LogOptions.Path=/var/logs/audit.log   --extra-config=apiserver.Audit.PolicyFile=/etc/kubernetes/addons/audit-policy.yaml
    minikube v0.35.0 on linux (amd64)
    Tip: Use 'minikube start -p &lt;name&gt;' to create a new cluster, or 'minikube delete' to delete this one.
    Restarting existing virtualbox VM for "minikube" ...
  ⌛  Waiting for SSH access ...
    "minikube" IP address is 192.168.99.101
    Configuring Docker as the container runtime ...
  ✨  Preparing Kubernetes environment ...
      ▪ apiserver.Authorization.Mode=RBAC
      ▪ apiserver.Audit.LogOptions.Path=/var/logs/audit.log
      ▪ apiserver.Audit.PolicyFile=/etc/kubernetes/addons/audit-policy.yaml
    Pulling images required by Kubernetes v1.13.4 ...
    Relaunching Kubernetes v1.13.4 using kubeadm ... 
  ⌛  Waiting for pods: apiserver
  </code></pre>
  
  <p>Why?</p>
  
  <p>I can do this</p>
  
  <pre><code>minkub start
  </code></pre>
  
  <p>Then I go for minikube ssh</p>
  
  <pre><code>$ sudo bash
  $ cd /var/logs
  bash: cd: /var/logs: No such file or directory
  ls
  cache  empty  lib  lock  log  run  spool  tmp
  </code></pre>
  
  <p>How to apply extra-config?</p>