oracle / oci-native-ingress-controller

OCI Native Ingress Controller
https://blogs.oracle.com/cloud-infrastructure/post/oracle-cloud-native-ingress-controller-kubernetes
Universal Permissive License v1.0
19 stars 21 forks source link

Mount Persistent Volume in many nodes doesnt work #82

Closed naguaramaster closed 3 months ago

naguaramaster commented 3 months ago

I am configuring a PersistentVolume that will serve as log storage for the created Pods. I've followed Oracle's documentation to create a PersistentVolume from an existing FileSystem, it doesn't seem complicated. The PersistentVolume was created, as well as the PersistentVolumeClaim without problems, I have applied the configurations in the deployment but it gives me the following error:

Deployment events:

TYPE REASON OBJECT MESSAGE 43m Normal Scheduled Pod/vista-crm-back-dp-86cc8989dd-mctfr Successfully assigned ns-apps/vista-crm-back-dp-86cc8989dd-mctfr to 10.220.11.168 43m Normal SuccessfulCreate ReplicaSet/vista-crm-back-dp-86cc8989dd Created pod: vista-crm-back-dp-86cc8989dd-mctfr 43m Normal ScalingReplicaSet Deployment/vista-crm-back-dp Scaled up replica set vista-crm-back-dp-86cc8989dd to 1 40m (x6 over 41m) Warning FailedMount Pod/vista-crm-back-dp-86cc8989dd-mctfr MountVolume.MountDevice failed for volume "fss-pv-desa" : rpc error: code = Aborted desc = An operation for the volume: ocid1.filesystem.oc1.iad.aaaaaaaaaah7quttnfqwillqojxwiotjmfsc2ylefuzaaaaa:10.220.11.170:/Logs_Desa_OKE already exists. 2m39s (x11 over 41m) Warning FailedMount Pod/vista-crm-back-dp-86cc8989dd-mctfr MountVolume.MountDevice failed for volume "fss-pv-desa" : rpc error: code = DeadlineExceeded desc = context deadline exceeded

the access mode is ReadWriteMany

PV apiVersion: v1 kind: PersistentVolume metadata: name: fss-pv-desa spec: capacity: storage: 50Gi volumeMode: Filesystem accessModes:

PVC apiVersion: v1 kind: PersistentVolumeClaim metadata: name: fss-pvc-desa namespace: ns-apps spec: accessModes:

plase help!