<p>Base question: When I try to use kube-apiserver on my master node, I get command not found error. How I can install/configure kube-apiserver? Any link to example will help.</p>

<pre><code>$ kube-apiserver --enable-admission-plugins DefaultStorageClass
-bash: kube-apiserver: command not found
</code></pre>

<p>Details: I am new to Kubernetes and Docker and was trying to create StatefulSet with volumeClaimTemplates. My problem is that the automatic PVs are not created and I get this message in the PVC log: "persistentvolume-controller  waiting for a volume to be created". I am not sure if I need to define DefaultStorageClass and so needed kube-apiserver to define it.</p>

<pre><code>Name:          nfs
Namespace:     default
StorageClass:  example-nfs
Status:        Pending
Volume:
Labels:        &lt;none&gt;
Annotations:   volume.beta.kubernetes.io/storage-provisioner=example.com/nfs
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
Events:
  Type    Reason                Age                  From                         Message
  ----    ------                ----                 ----                         -------
  Normal  ExternalProvisioning  3m (x2401 over 10h)  persistentvolume-controller  waiting for a volume to be created, either by external provisioner "example.com/nfs" or manually created by system administrator
</code></pre>

<p>Here is get pvc result:</p>

<pre><code>$ kubectl get pvc
NAME      STATUS    VOLUME    CAPACITY   ACCESS MODES   STORAGECLASS   AGE
nfs       Pending                                       example-nfs    10h
</code></pre>

<p>And get storageclass:</p>

<pre><code>$ kubectl describe storageclass example-nfs
Name:                  example-nfs
IsDefaultClass:        No
Annotations:           &lt;none&gt;
Provisioner:           example.com/nfs
Parameters:            &lt;none&gt;
AllowVolumeExpansion:  &lt;unset&gt;
MountOptions:          &lt;none&gt;
ReclaimPolicy:         Delete
VolumeBindingMode:     Immediate
Events:                &lt;none&gt;
</code></pre>

<p>How can I troubleshoot this issue (e.g. logs for why the storage was not created)?</p>

<p>You are asking two different questions here, one about kube-apiserver configuration, one about troubleshooting your <code>StorageClass</code>.</p>

<p>Here's an answer for your first question:</p>

<p><code>kube-apiserver</code> is running as a Docker container on your master node. Therefore, the binary is <em>within</em> the container, not on your host system. It is started by the master's <code>kubelet</code> from a file located at <code>/etc/kubernetes/manifests</code>. <code>kubelet</code> is watching this directory and will start any Pod defined here as "static pods".</p>

<p>To configure <code>kube-apiserver</code> command line arguments you need to modify <code>/etc/kubernetes/manifests/kube-apiserver.yaml</code> on your master.</p>
