<p>I deployed my first container, I got info:</p>
<pre><code>deployment.apps/frontarena-ads-deployment created
</code></pre>
<p>but then I saw my container creation is stuck in Waiting status.
Then I saw the logs using <code>kubectl describe pod frontarena-ads-deployment-5b475667dd-gzmlp</code> and saw MountVolume error which I cannot figure out why it is thrown:</p>
<blockquote>
<p>Warning  FailedMount  9m24s  kubelet            MountVolume.SetUp
failed for volume &quot;ads-filesharevolume&quot; : mount failed: exit status 32 Mounting command:
systemd-run Mounting arguments: --description=Kubernetes transient
mount for
/var/lib/kubelet/pods/85aa3bfa-341a-4da1-b3de-fb1979420028/volumes/kubernetes.io~azure-file/ads-filesharevolume
--scope -- mount -t cifs -o username=frontarenastorage,password=mypassword,file_mode=0777,dir_mode=0777,vers=3.0
//frontarenastorage.file.core.windows.net/azurecontainershare
/var/lib/kubelet/pods/85aa3bfa-341a-4da1-b3de-fb1979420028/volumes/kubernetes.io~azure-file/ads-filesharevolume
Output: Running scope as unit
run-rf54d5b5f84854777956ae0e25810bb94.scope. mount error(115):
Operation now in progress Refer to the mount.cifs(8) manual page (e.g.
man mount.cifs)</p>
</blockquote>
<p>Before I run the deployment I created a secret in Azure, using the already created azure file share, which I referenced within the YAML.</p>
<pre><code>$AKS_PERS_STORAGE_ACCOUNT_NAME=&quot;frontarenastorage&quot;
$STORAGE_KEY=&quot;mypassword&quot;
kubectl create secret generic fa-fileshare-secret --from-literal=azurestorageaccountname=$AKS_PERS_STORAGE_ACCOUNT_NAME --from-literal=azurestorageaccountkey=$STORAGE_KEY
</code></pre>
<p>In that file share I have folders and files which I need to mount and I reference <strong>azurecontainershare</strong> in YAML:
<a href="https://i.stack.imgur.com/Yncpx.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Yncpx.png" alt="enter image description here" /></a></p>
<p>My YAML looks like this:</p>
<pre><code>apiVersion: apps/v1
kind: Deployment
metadata:
  name: frontarena-ads-deployment
  labels:
    app: frontarena-ads-deployment
spec:
  replicas: 1
  template:
    metadata:
      name: frontarena-ads-aks-test
      labels:
        app: frontarena-ads-aks-test
    spec:
      containers:
      - name: frontarena-ads-aks-test
        image: faselect-docker.dev/frontarena/ads:test1
        imagePullPolicy: Always
        ports:
          - containerPort: 9000
        volumeMounts:
          - name: ads-filesharevolume
            mountPath: /opt/front/arena/host
      volumes:
      - name: ads-filesharevolume
        azureFile:
          secretName: fa-fileshare-secret
          shareName: azurecontainershare
          readOnly: false
      imagePullSecrets:
        - name: fa-repo-secret
  selector:
    matchLabels:
      app: frontarena-ads-aks-test
</code></pre>

<p>The Issue was because of the different Azure Regions in which AKS cluster and Azure File Share are deployed. If they are in the same Region you would not have this issue.</p>
