问题描述
我正在尝试使用RabbitMQ集群Kubernetes运算符创建RabbitMQ实例,但是PersistentVolumeClaims存在问题。我正在使用适用于Windows的Docker桌面运行Kubernetes 1.18.8。
我已经这样安装了操作员:
kubectl apply -f "https://github.com/rabbitmq/cluster-operator/releases/latest/download/cluster-operator.yml"
我已经根据文档为实例创建了一个非常简单的配置:
apiVersion: rabbitmq.com/v1beta1
kind: RabbitmqCluster
metadata:
name: nccrabbitmqcluster
似乎已经创建了应该创建的所有对象,但是吊舱陷入了待处理状态:
$ kubectl get all | grep rabbit
pod/nccrabbitmqcluster-server-0 0/1 Pending 0 14m
service/nccrabbitmqcluster ClusterIP 10.100.186.115 <none> 5672/TCP,15672/TCP 14m
service/nccrabbitmqcluster-nodes ClusterIP None <none> 4369/TCP,25672/TCP 14m
statefulset.apps/nccrabbitmqcluster-server 0/1 14m
根据广告连播的事件,似乎有未绑定的PVC:
$ kubectl describe pod/nccrabbitmqcluster-server-0 | tail -n 5
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling <unknown> default-scheduler running "VolumeBinding" filter plugin for pod "nccrabbitmqcluster-server-0": pod has unbound immediate PersistentVolumeClaims
Warning FailedScheduling <unknown> default-scheduler running "VolumeBinding" filter plugin for pod "nccrabbitmqcluster-server-0": pod has unbound immediate PersistentVolumeClaims
根据PVC的事件,它正在等待创建卷:
$ kubectl describe pvc persistence-nccrabbitmqcluster-server-0
Name: persistence-nccrabbitmqcluster-server-0
Namespace: default
StorageClass: hostpath
Status: Pending
Volume:
Labels: app.kubernetes.io/component=rabbitmq
app.kubernetes.io/name=nccrabbitmqcluster
app.kubernetes.io/part-of=rabbitmq
Annotations: volume.beta.kubernetes.io/storage-provisioner: docker.io/hostpath
Finalizers: [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode: Filesystem
Mounted By: nccrabbitmqcluster-server-0
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal ExternalProvisioning 27s (x23 over 19m) persistentvolume-controller waiting for a volume to be created,either by external provisioner "docker.io/hostpath" or manually created by system administrator
我的理解是docker.io/hostpath是正确的供应者:
$ kubectl get storageclasses
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
hostpath (default) docker.io/hostpath Delete Immediate false 20d
我看不到任何与PCS相关的PV:
$ kubectl get pv | grep rabbit
为什么不自动创建该卷,我该怎么办?
解决方法
是的,您的本地主机路径不能用作动态卷配置器。该操作符需要一个可以动态创建 PV 的存储类名。 在您的情况下,您的运营商一直在等待 PV 的创建。相反,如果您在本地机器上进行操作,您可以手动创建 PV 和 PVC。 检查这个例子 - https://github.com/rabbitmq/cluster-operator/blob/main/docs/examples/multiple-disks/rabbitmq.yaml
如果您打算尝试像 AWS 这样的任何云提供商,那么这很容易。在您的集群中部署 EBS CSI 驱动程序,这将为您创建一个存储类,该存储类将配置动态卷。