Pod creation stuck when used more than one mounted volumes

[maximzhemerenko]

Hi, thank you for this amazing repo! I use this driver in my projects and it very helps me.

But I noticed the one problem: if I use more than one gcs volumes my pod is never started, stucks in the creating state and I see the status message say that there are unmourned volume (one of two). When I use one of any volume - everything is good. When I use one volume in different pods - it working too. But only not two at the same time.

Could you help me please with this problem?

[ofek]

Hello! Can you show yaml?

[maximzhemerenko]

apiVersion: apps/v1
kind: Deployment
metadata:
  name: {{ include "sync1to1.fullname" . }}-backend
  labels:
    {{- include "sync1to1.labels" . | nindent 4 }}
spec:
  replicas: {{ .Values.replicas.backend }}
  selector:
    matchLabels:
      {{- include "sync1to1.selectorLabels" . | nindent 6 }}
      app.sync1to1.com/app: backend
  template:
    metadata:
      labels:
        {{- include "sync1to1.labels" . | nindent 8 }}
        app.sync1to1.com/app: backend
    spec:
      containers:
        - name: {{ .Chart.Name }}
          image: {{ include "sync1to1.images.backend" . }}
          ports:
            - containerPort: 80
         
          volumeMounts:
          - name: gcs
            mountPath: /data/files
      imagePullSecrets:
        - name: {{ include "sync1to1.fullname" . }}-dockerconfigjson
      volumes:
        - name: gcs
          persistentVolumeClaim:
            claimName: {{ include "sync1to1.fullname" . }}-files

[maximzhemerenko]

I use the easiest configuration, and if I mound one volume it works) but not two. I tested, if I use not gcs volumes (Kubernetes default storage class) 2 volume mount works too