0

我的部署是关于 Wordpress 和 MYsql。我已经定义了一个新的池和一个新的命名空间，我试图让我的 pod 从这个定义的新池中获取一个 IP 地址，但它们永远不会得到一个。

我的命名空间文件 yaml

apiVersion: v1
kind: Namespace
metadata:
  name: produccion
  annotations:
    cni.projectcalico.org/ipv4pools: ippool

我的池代码

calicoctl create -f -<<EOF
apiVersion: projectcalico.org/v3
kind: IPPool
metadata:
   name: ippool
spec:
   cidr: 192.169.0.0/24
   blockSize: 29
   ipipMode: Always
   natOutgoing: true
EOF

我的mysql部署是

apiVersion: v1
kind: Service
metadata:
  name: wordpress-mysql   
  namespace: produccion
  labels:                 
    app: wordpress
spec:
  ports:
    - port: 3306
      targetPort: 3306
      nodePort: 31066
  selector:
    app: wordpress
    tier: mysql
  type: NodePort
---
apiVersion:  apps/v1
kind: Deployment
metadata:
  name: wordpress-mysql
  namespace: produccion
  annotations:
    cni.projectcalico.org/ipv4pools: ippool
  labels:
    app: wordpress
spec:
  selector:
    matchLabels:
      app: wordpress
      tier: mysql
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: wordpress
        tier: mysql
    spec:
      containers:
      - image: mysql
        name: mysql
        env:
        - name: MYSQL_ROOT_PASSWORD
          value: PASS
        ports:
        - containerPort: 3306
          name: mysql
        volumeMounts:
        - name: mysql-persistent-storage 
          mountPath: "/var/lib/mysql"
      volumes:
      - name: mysql-persistent-storage 
        persistentVolumeClaim:
          claimName: mysql-pv-claim

我的 wordpress 部署

apiVersion: v1
kind: Service
metadata:
  name: wordpress
  namespace: produccion
  labels:
    app: wordpress
spec:
  ports:
    - port: 80
      nodePort: 30999
  selector:
    app: wordpress
    tier: frontend
  type: NodePort
---
apiVersion: apps/v1 
kind: Deployment
metadata:
  name: wordpress
  namespace: produccion
  labels:
    app: wordpress
spec:
  selector:
    matchLabels:
      app: wordpress
      tier: frontend
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: wordpress
        tier: frontend
    spec:
      containers:
      - image: wordpress
        name: wordpress
        env:
        - name: WORDPRESS_DB_NAME
          value: wordpress
        - name: WORDPRESS_DB_HOST
          value: IP_Address:31066
        - name: WORDPRESS_DB_USER
          value: root
        - name: WORDPRESS_DB_PASSWORD
          value: PASS
        ports:
        - containerPort: 80
          name: wordpress
        volumeMounts:
        - name: wordpress-persistent-storage
          mountPath: "/var/www/html"          
      volumes:
      - name: wordpress-persistent-storage
        persistentVolumeClaim:
          claimName: wordpress-persistent-storage

此外，我还为每个服务（mysql 和 wordpress）提供了两个 PV yaml 文件。

当我执行任何部署的 Kubectl 时，它们停留在ContainerCreating并且 IP 列停留在none。

produccion             wordpress-mysql-74578f5d6d-knzzh             0/1     ContainerCreating   0          70m    <none>           dockerc8.tecsinfo-ec.com

如果我检查这个 pod，我会收到下一个错误：

Normal   Scheduled               88s                             default-scheduler  Successfully assigned produccion/wordpress-mysql-74578f5d6d-65jvt to dockerc8.tecsinfo-ec.com
  Warning  FailedCreatePodSandBox  <invalid>                       kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "cdb1460246562cac11a57073ab12489dc169cb72aa3371cb2e72489544812a9b" network for pod "wordpress-mysql-74578f5d6d-65jvt": networkPlugin cni failed to set up pod "wordpress-mysql-74578f5d6d-65jvt_produccion" network: invalid character 'i' looking for beginning of value
  Warning  FailedCreatePodSandBox  <invalid>                       kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "672a2c35c2bb99ebd5b7d180d4426184613c87f9bc606c15526c9d472b54bd6f" network for pod "wordpress-mysql-74578f5d6d-65jvt": networkPlugin cni failed to set up pod "wordpress-mysql-74578f5d6d-65jvt_produccion" network: invalid character 'i' looking for beginning of value
  Warning  FailedCreatePodSandBox  <invalid>                       kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "de4d7669206f568618a79098d564e76899779f94120bddcee080c75f81243a85" network for pod "wordpress-mysql-74578f5d6d-65jvt": networkPlugin cni failed to set up pod "wordpress-mysql-74578f5d6d-65jvt_produccion" network: invalid character 'i' looking for beginning of value

我正在使用互联网上的一些指南，例如：https ://www.projectcalico.org/calico-ipam-explained-and-enhanced/ ，但即使这在我的实验室也不起作用。

我对使用 Kubernetes 还是很陌生，我不知道还能做什么或检查什么。

4

1 回答 1

1

根据此处的 Project Calico 文档，您的错误是由于 YAML 中的无效值造成的：使用 Kubernetes 注释

您需要提供 IP 池列表作为注释中的值，而不是单个字符串。以下代码段应该适合您。

cni.projectcalico.org/ipv4pools: "[\"ippool\"]"
于 2021-06-17T16:20:06.983 回答