我正在尝试按照https://docs.confluent.io/current/installation/operator/co-deployment.html#kubernetes-deployment上的说明进行操作,但无法获取它来配置存储。我假设它应该自动发生,因为我有一个默认存储集。有什么建议吗?
global:
provider:
name: private
## if any name which indicates regions
##
region: us-south
kubernetes:
deployment:
## If kubernetes is deployed in multi zone mode then specify availability-zones as appropriate
## If kubernetes is deployed in single availability zone then specify appropriate values
## For the private cloud, use kubernetes node labels as appropriate
zones:
- dal10
## more information can be found here
## https://kubernetes.io/docs/concepts/storage/storage-classes/
storage:
## Use Retain if you want to persist data after CP cluster has been uninstalled
reclaimPolicy: Delete
provisioner: ibm.io/ibmc-block
parameters:
billingType: hourly
classVersion: "2"
fsType: ext4
iopsPerGB: "2"
sizeRange: '[20-12000]Gi'
type: Endurance
kubectl get storageclass
NAME PROVISIONER AGE
ibmc-block-bronze (default) ibm.io/ibmc-block 3h38m
ibmc-block-custom ibm.io/ibmc-block 3h38m
ibmc-block-gold ibm.io/ibmc-block 3h38m
ibmc-block-retain-bronze ibm.io/ibmc-block 3h38m
ibmc-block-retain-custom ibm.io/ibmc-block 3h38m
ibmc-block-retain-gold ibm.io/ibmc-block 3h38m
ibmc-block-retain-silver ibm.io/ibmc-block 3h38m
ibmc-block-silver ibm.io/ibmc-block 3h38m
zookeeper-standard-ssd-dal10 ibm.io/ibmc-block 37m
kubectl get pvc -n operator
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
data-zookeeper-0 Pending zookeeper-standard-ssd-dal10 43m
data-zookeeper-1 Pending zookeeper-standard-ssd-dal10 43m
data-zookeeper-2 Pending zookeeper-standard-ssd-dal10 43m
txnlog-zookeeper-0 Pending zookeeper-standard-ssd-dal10 43m
txnlog-zookeeper-1 Pending zookeeper-standard-ssd-dal10 43m
txnlog-zookeeper-2 Pending zookeeper-standard-ssd-dal10 43m
kubectl describe pvc -n operator data-zookeeper-0
Name: data-zookeeper-0
Namespace: operator
StorageClass: zookeeper-standard-ssd-dal10
Status: Pending
Volume:
Labels: namespace=operator
type=zookeeper
Annotations: volume.beta.kubernetes.io/storage-provisioner: ibm.io/ibmc-block
Finalizers: [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode: Filesystem
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal ExternalProvisioning 3m39s (x163 over 43m) persistentvolume-controller waiting for a volume to be created, either by external provisioner "ibm.io/ibmc-block" or manually created by system administrator
Mounted By: zookeeper-0
kubectl get pods -n operator
pods -n operator
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
cc-manager-56cb486b44-pw7xv 1/1 Running 1 176m 172.30.99.182 10.240.0.8 <none> <none>
cc-operator-587f657c77-mnxrq 1/1 Running 0 176m 172.30.99.162 10.240.0.8 <none> <none>
zookeeper-0 0/1 Pending 0 27s <none> <none> <none> <none>
zookeeper-1 0/1 Pending 0 27s <none> <none> <none> <none>
zookeeper-2 0/1 Pending 0 27s <none> <none> <none> <none>
kubectl describe pod -n operator zookeeper-0
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 33s (x2 over 33s) default-scheduler pod has unbound immediate PersistentVolumeClaims
进一步进行,然后执行kubectl describe pv <pvname>
以查看发生了什么。