I have followed the instructions here and facing a problem. 1. As explained I have mounted a PVC to teh audit pod,, which is a azure blob storage account I share below the pv-pvc yaml file and the transformer file which is added to the kustomization and I have rebuilt and applied the new site. kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: pvc-audit
namespace: sasprod
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 10Gi
volumeName: pv-audit
storageClassName: azureblob-nfs-premium
---
apiVersion: v1
kind: PersistentVolume
metadata:
name: pv-audit
namespace: sasprod
spec:
capacity:
storage: 10Gi
accessModes:
- ReadWriteMany
persistentVolumeReclaimPolicy: Retain # If set as "Delete" container would be removed after pvc deletion
storageClassName: azureblob-nfs-premium
csi:
driver: blob.csi.azure.com
readOnly: false
# make sure volumeid is unique for every identical storage blob container in the cluster
# character `#` is reserved for internal use and cannot be used in volumehandle
volumeHandle: audit-logs
volumeAttributes:
resourceGroup: dpi-bsdm-sasprod-rg
storageAccount: dpibsdmsasprodtest
containerName: audit-logs
protocol: nfs transformers file apiVersion: builtin kind: PatchTransformer metadata: name: archive-transformer patch: |- - op: add path: /spec/template/spec/volumes/- value: name: audit-archive-volume persistentVolumeClaim: claimName: pvc-audit - op: add path: /spec/template/spec/containers/0/volumeMounts/- value: name: audit-archive-volume mountPath: /archive target: group: apps kind: Deployment name: sas-audit version: v1 This pvc is bound succesfully as I can see it when I shell into the audit pod. Below is the audit pod configuration However, I get these error notifications Could you help why the archiving is not going as expected?
... View more
