We are trying to spin up a Stateful MQ manager with Azure File System as persistent storage mounted for data in an Azure Kubernetes cluster. For this, creating a file share in Azure and have created secret in Azure Kubernetes with file share account name and account key as shown below.

kubectl create secret generic mq-secret --from-literal=azurestorageaccountname=**** --from-literal=azurestorageaccountkey=*********************

After that, we have created PVC and PV for persistence storage using this Azure file share. here is my PVC, PV and deployment configuration file.

---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: mqfilesharepv
  labels:
    usage: mqfilesharepv
spec:
  capacity:
    storage: 2Gi
  accessModes:
    - ReadWriteMany
  persistentVolumeReclaimPolicy: Retain
  azureFile:
    # Replace with your secret name
    secretName: mq-secret
    # Replace with correct storage share name
    shareName: mqfileshare
    # In case the secret is stored in a different namespace
    #shareNamespace: default
    readOnly: false
  mountOptions:
  - dir_mode=0755
  - file_mode=0755
  - uid=999
  - gid=999
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: mqfilesharepvc
  annotations:
    volume.beta.kubernetes.io/storage-class: ""
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 2Gi
  selector:
    matchLabels:
      usage: mqfilesharepv
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: ibmmq-deployment1
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: ibmmq1
        version: v4
    spec:
      securityContext:
        fsGroup: 999
        #runAsGroup: 999
        runAsUser: 0
      containers:
      - name: ibmmq1
        #image: miraclelabsregistry008.azurecr.io/ibmmq:9.1.1.0
        image: ibmcom/mq:9.1.2.0
        env:
         - name: LICENSE
           value: accept
         - name: MQ_QMGR_NAME
           value: QM1
        imagePullPolicy: IfNotPresent
        ports:
        - name: port1414
          containerPort: 1414
        - name: port9443
          containerPort: 9443
        volumeMounts:
        - mountPath: "/mnt/mqm"
          name: test-storage
      volumes:
      - name: test-storage
        persistentVolumeClaim:
        claimName: mqfilesharepvc
---
apiVersion: v1
kind: Service
metadata:
  name: qm
  labels:
    app: ibmmq1
    version: v4
spec:
  type:LoadBalancer
  ports:
  - name: port1414
  port: 1414
  - name: port9443
  port: 9443
  selector:
    app: ibmmq1
    version: v4

Now, we can able to deploy the MQ image in Azure Kubernetes, but pod gets restarted multiple times and generating the logs as shown below and unable to get the UI of IBM Websphere MQ.

2019-05-30T16:56:48.340Z Starting web server 2019-05-30T16:56:53.650Z Error 22 starting web server: Starting server mqweb. Server mqweb start failed. Check server logs for details.

2019-05-30T16:57:07.113Z crtmqm returned 71 2019-05-30T16:57:07.113Z AMQ8101S: IBM MQ error (893) has occurred.

2019-05-30T16:57:07.114Z /usr/bin/crtmqm: exit status 71

so, what might be the issue? and Could anybody help me to resolve this error?