pod具有未绑定的即时PersistentVolumeClaims ops经理 [英] pod has unbound immediate PersistentVolumeClaims ops manager

查看:1075
本文介绍了pod具有未绑定的即时PersistentVolumeClaims ops经理的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

请看下面

我是新手,尝试使用kubeadm用2台物理计算机构建本地集群.我正在关注 https://github.com/mongodb/mongodb-enterprise-kubernetes步骤,一切正常.起初,我正在安装kubernetes运算符,但是当我尝试安装ops Manager时,我得到了: 0/2节点可用:2个容器具有未绑定的即时PersistentVolumeClaims ops管理器. 我用来安装ops Manager的Yaml是:

I am new trying to build a local cluster with 2 physical machines with kubeadm. I am following this https://github.com/mongodb/mongodb-enterprise-kubernetes steps and everything is ok. At first i am installing kubernetes operator, but when i tried to install ops manager i am geting: 0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims ops manager. the yaml i used to install ops manager is:

  ---
    apiVersion: mongodb.com/v1
    kind: MongoDBOpsManager
    metadata:
    
      name: opsmanager1
    
    spec:
    
      replicas: 2
    
      version: 4.2.0
    
      adminCredentials: mongo-db-admin1 # Should match metadata.name
    
                                               # in the Kubernetes secret
    
                                               # for the admin user
    
      externalConnectivity:
    
        type: NodePort
    
    
    
      applicationDatabase:
    
        members: 3
    
        version: 4.4.0
    
        persistent: true
    
        podSpec:
       
           persistence:
    
             single: 
    
               storage: 1Gi

我不知道是什么问题.我处于测试阶段,我的目标是建立一个可伸缩的mongo数据库.预先感谢

i can't figure out what the problem is. I am at a testing phase, and my goal is to make a scaling mongo database. Thanks in advance

编辑:我做了一些更改.我创建了这样的存储类:

edit: i made a few changes.I created storage class like this:

    apiVersion: storage.k8s.io/v1
    kind: StorageClass
    metadata:
    
      name: localstorage
    
    provisioner: kubernetes.io/no-provisioner
    volumeBindingMode: Immediate
    reclaimPolicy: Delete
    allowVolumeExpansion: True
    
    ---
    kind: PersistentVolume
    apiVersion: v1
    metadata:
      name: mongo-01
      labels:
        type: local
    spec:
      storageClassName: localstorage
      capacity:
        storage: 2Gi
      accessModes:
        - ReadWriteOnce
      hostPath:
        path: "/home/master/mongo01"
    
    ---
    kind: PersistentVolume
    apiVersion: v1
    metadata:
      name: mongo-02
      labels:
        type: local
    spec:
      storageClassName: localstorage
      capacity:
        storage: 2Gi
      accessModes:
        - ReadWriteOnce
      hostPath:
        path: "/home/master/mongo02"

现在我对运维经理的看法是:

And now my yaml for ops manger is:

apiVersion: mongodb.com/v1
kind: MongoDBOpsManager
metadata:
 name: ops-manager-localmode
spec:
 replicas: 2
 version: 4.2.12
 adminCredentials: mongo-db-admin1
 externalConnectivity:
    type: NodePort
 
 statefulSet:
   spec:
     # the Persistent Volume Claim will be created for each Ops Manager Pod
     volumeClaimTemplates:
       - metadata:
           name: mongodb-versions
         spec:
           storageClassName: localstorage
           accessModes: [ "ReadWriteOnce" ]
           resources:
             requests:
               storage: 2Gi
     template:
       spec:
         containers:
           - name: mongodb-ops-manager
             volumeMounts:
               - name: mongodb-versions
                 # this is the directory in each Pod where all MongoDB
                 # archives must be put
                 mountPath: /mongodb-ops-manager/mongodb-releases

 backup:
   enabled: false

 applicationDatabase:
   members: 3
   version: 4.4.0

   persistent: true

但是我收到一个新错误:警告ProvisioningFailed 44s(x6超过6m53s)persistentvolume-controller没有卷插件匹配名称:kubernetes.io/no-provisioner

But i get a new error : Warning ProvisioningFailed 44s (x26 over 6m53s) persistentvolume-controller no volume plugin matched name: kubernetes.io/no-provisioner

推荐答案

乍一看,您似乎没有任何可以在集群上创建PVC的卷.参见 https://v1-15.docs.kubernetes.io/docs/concepts/storage/volumes/ 您的应用程序需要创建一个持久卷,但是您的集群不知道该怎么做.

At a quick glance, it looks like you don't have any volume that can create a PVC on your cluster. see https://v1-15.docs.kubernetes.io/docs/concepts/storage/volumes/ Your app needs to create a persistant volume, but your cluster doesn't know how to do that.

这篇关于pod具有未绑定的即时PersistentVolumeClaims ops经理的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆