<p>I'm trying to follow along the Hashicorp docs to set up a Vault instance</p>

<p><a href="https://www.youtube.com/watch?v=_r368h-mxxs&amp;t=94s" rel="nofollow noreferrer">https://www.youtube.com/watch?v=_r368h-mxxs&amp;t=94s</a>
<a href="https://www.vaultproject.io/docs/platform/k8s/helm/run/" rel="nofollow noreferrer">https://www.vaultproject.io/docs/platform/k8s/helm/run/</a></p>

<p>To start of with the initialisation I run</p>

<pre><code>helm --namespace=myvault --name=vault .
</code></pre>

<p>But when I try to initialise the Vault instance itself with</p>

<pre><code>kubectl --namespace=vault exec -it vault-0 -- vault operator init
</code></pre>

<p>I get the error</p>

<pre><code>Error from server (BadRequest): pod vault-0 does not have a host assigned
</code></pre>

<p>Running</p>

<pre><code>kubectl --namespace=vault describe pods vault-0
</code></pre>

<p>gives the error </p>

<pre><code>Warning  FailedScheduling  60s (x21 over 10m)  default-scheduler  pod has unbound immediate PersistentVolumeClaims (repeated 3 times)
</code></pre>

<p>Is there a setting that I'm missing and not shown in the docs that needs set for this to work?</p>

<p>Running on prem Centos 7 cluster with 3 nodes</p>

CEamonn
<p>Vault is deployed as StatefulSet which has <code>volumeClaimTemplates</code></p>

<pre><code>volumeClaimTemplates:
  - metadata:
      creationTimestamp: null
      name: data
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 10Gi
      volumeMode: Filesystem
</code></pre>

<p>It seems for some reason the PVC and PV is not created and the pod needs to be bound to a PVC before it can be started. Below commands should give some clue.</p>

<pre><code>kubectl describe pvc
kubectl describe pv
kubectl describe sc
</code></pre>

<p>If there is no default storage class you may need to create it so that the PersistentVolumeClaim can take the storage from there</p>
