0

有什么问题？

我无法让使用卷的 pod 运行。在 Kubernetes 仪表板中，我收到以下错误：

为 pod“influxdb-6979bff6f9-hpf89”运行“VolumeBinding”过滤器插件：pod 具有未绑定的立即 PersistentVolumeClaims

我做了什么？

运行Kompose convert到我的docker-compose.yml文件后，我尝试使用micro8ks kubectl apply -f .（我正在使用 micro8ks）启动 pod，我不得不将 networkpolicy yaml 文件的版本替换为networking.k8s.io/v1（参见此处），但除了此更改之外，我没有更改任何内容。

YAML 文件

influxdb-deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    kompose.cmd: ./kompose convert
    kompose.version: 1.21.0 (992df58d8)
  creationTimestamp: null
  labels:
    io.kompose.service: influxdb
  name: influxdb
spec:
  replicas: 1
  selector:
    matchLabels:
      io.kompose.service: influxdb
  strategy:
    type: Recreate
  template:
    metadata:
      annotations:
        kompose.cmd: ./kompose convert
        kompose.version: 1.21.0 (992df58d8)
      creationTimestamp: null
      labels:
        io.kompose.network/cloud-net: "true"
        io.kompose.network/default: "true"
        io.kompose.service: influxdb
    spec:
      containers:
      - env:
        - name: INFLUXDB_HTTP_LOG_ENABLED
          value: "false"
        image: influxdb:1.8
        imagePullPolicy: ""
        name: influxdb
        ports:
        - containerPort: 8086
        resources: {}
        volumeMounts:
        - mountPath: /var/lib/influxdb
          name: influx
      restartPolicy: Always
      serviceAccountName: ""
      volumes:
      - name: influx
        persistentVolumeClaim:
          claimName: influx
status: {}

influxdb-service.yaml

apiVersion: v1
kind: Service
metadata:
  annotations:
    kompose.cmd: ./kompose convert
    kompose.version: 1.21.0 (992df58d8)
  creationTimestamp: null
  labels:
    io.kompose.service: influxdb
  name: influxdb
spec:
  ports:
  - name: "8087"
    port: 8087
    targetPort: 8086
  selector:
    io.kompose.service: influxdb
status:
  loadBalancer: {}

流入持久化卷声明.yaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  creationTimestamp: null
  labels:
    io.kompose.service: influx
  name: influx
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 100Mi
status: {}
4

1 回答 1

2

如果PersistentVolumeClaim集群没有StorageClass可以动态配置的 aPersistentVolume或者它没有手动创建PersistentVolume来满足PersistentVolumeClaim

这是有关如何配置要使用的 pod的指南PersistentVolume

要解决当前场景，您可以手动创建 PV

apiVersion: v1
kind: PersistentVolume
metadata:
  name: task-pv-volume
  labels:
    type: local
spec:
  storageClassName: manual
  capacity:
    storage: 100Mi
  accessModes:
    - ReadWriteOnce
  hostPath:
    path: "/mnt/data"

请注意hostPath仅作为示例的用法。不建议用于生产用途。考虑使用此处支持的类型的外部块或文件存储

于 2020-06-23T15:04:13.597 回答