如何解决Kubernetes:在同一PersistentVolume中使用两个VolumeMount
可以在AKS中为两个不同的VolumeMount使用相同的Persistent Volume / PVC,这是我正在尝试的:
Pod Deploy /在这里,我在同一PersistentVolumeClaim中设置了两个VolumeMount
(...)
volumeMounts:
- name: data1
mountPath: /opt/data/data1
subPath: data1
- name: data2
mountPath: /opt/data/data2
subPath: data2
volumes:
- name: data1
persistentVolumeClaim:
claimName: pv-data
- name: data2
persistentVolumeClaim:
claimName: pv-data
(...)
在Pod部署中定义的data1和data2卷使用的持久卷声明
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: pv-data
spec:
accessModes:
- ReadWriteMany # or ReadWriteOnce
storageClassName: pv-storage
resources:
requests:
storage: 40Gi
持久量
apiVersion: v1
kind: PersistentVolume
metadata:
name: pvdisk
spec:
capacity:
storage: 40Gi
storageClassName: pv-storage
azureDisk:
kind: Managed
diskName: disk1
diskURI: /subscriptions/xxxxx/resourceGroups/xxxx/providers/Microsoft.Compute/disks/disk1
fsType: ext4
accessModes:
- ReadWriteMany
persistentVolumeReclaimPolicy: Retain
claimRef:
name: pv-data
namespace: default
当尝试应用此“想法”时,出现以下错误:
找不到persistentvolumeclaim“ data1” 警告FailedScheduling 1s(x2超过5s)默认调度程序窗格有立即绑定的PersistentVolumeClaims(已重复2次)
谢谢 蒂亚戈
编辑 kubectl描述pvc pv数据
Name: sonar-data
Namespace: default
StorageClass: sonar-storage
Status: Bound
Volume: pvdisk
Labels: <none>
Annotations: pv.kubernetes.io/bind-completed: yes
pv.kubernetes.io/bound-by-controller: yes
Finalizers: [kubernetes.io/pvc-protection]
Capacity: 40Gi
Access Modes: RWO
VolumeMode: Filesystem
Mounted By: pod-69d6c8d89c-8t5lb
pod-69d6c8d89c-8t5lb
kubectl描述了pv pvdisk
Name: pvdisk
Finalizers: [kubernetes.io/pv-protection]
StorageClass: sonar-storage
Status: Bound
Claim: default/data
Reclaim Policy: Retain
Access Modes: RWO
VolumeMode: Filesystem
Capacity: 40Gi
Message:
Source:
Type: AzureDisk (an Azure Data Disk mount on the host and bind mount to the pod)
DiskName: XXXXXX
DiskURI: XXXXXX
Kind: Managed
FSType: ext4
CachingMode: ReadWrite
ReadOnly: false
Events: <none>
荚形容
Volumes:
data1:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: data1
ReadOnly: pv-data
config-volume:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: data-config
Optional: false
data2:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: pv-data
ReadOnly: false
(...)
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedMount 2m21s (x63 over 142m) kubelet,aks-pool1-19402761-vmss000002 Unable to mount volumes for pod "pod-69d6c8d89c-8t5lb_default(77795ef3-6c88-480a-b3ed-18b9453c742a)": timeout expired waiting for volumes to attach or mount for pod "default"/"pod-69d6c8d89c-8t5lb". list of unmounted volumes=[data1]. list of unattached volumes=[data1 config-volume data2 default-token-nhrrv]
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。