Question

我不确定为什么没有声明持久性卷，或者我可以采取哪些步骤来进一步诊断？

索赔大小是否与卷大小相符？卷大小是否应与GCP卷大小匹配？

这很难测试并弄清楚......

我的目标只是能够创建一个包含单个副本的Wordpress实例，只要它支持滚动部署即可....

kubectl get pods的输出：

NAME                         READY     STATUS    RESTARTS   AGE
wordpress-1546832918-mz4rt   0/3       Pending   0          47m
wordpress-1546832918-p0s1s   0/3       Pending   0          47m

kubectl describe pods的输出：

...truncated...
Events:
  FirstSeen LastSeen    Count   From            SubObjectPath   Type        Reason          Message
  --------- --------    -----   ----            -------------   --------    ------          -------
  47m       3s      168 default-scheduler       Warning     FailedScheduling    [SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "task-pv-claim", which is unexpected., SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "task-pv-claim", which is unexpected.]

kubectl get pvc的输出：

NAME            STATUS    VOLUME    CAPACITY   ACCESSMODES   STORAGECLASS   AGE
task-pv-claim   Pending                                      manual         4h

kubectl get pv的输出：

NAME      CAPACITY   ACCESSMODES   RECLAIMPOLICY   STATUS      CLAIM     STORAGECLASS   REASON    AGE
pv0001    10Gi       RWX           Retain          Available             manual                   4h

production.yaml

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: wordpress
  labels:
    app: wordpress
spec:
  replicas: 2
  selector:
    matchLabels:
      app: wordpress
  template:
    metadata:
      labels:
        app: wordpress
    spec:
      terminationGracePeriodSeconds: 30
      containers:
        - image: eu.gcr.io/abcxyz/wordpress:deploy-1502807720
          name: wordpress
          imagePullPolicy: "Always"
          env:
            - name: WORDPRESS_HOST
              value: localhost
            - name: WORDPRESS_DB_USERNAME
              valueFrom:
                secretKeyRef:
                  name: cloudsql-db-credentials
                  key: username
          volumeMounts:
            - name: wordpress-persistent-storage
              mountPath: /var/www/html
        - image: eu.gcr.io/abcxyz/nginx:deploy-1502807720
          name: nginx
          imagePullPolicy: "Always"
          ports:
            - containerPort: 80
              name: nginx
          volumeMounts:
            - name: wordpress-persistent-storage
              mountPath: /var/www/html
              readOnly: true
        - image: gcr.io/cloudsql-docker/gce-proxy:1.09
          name: cloudsql-proxy
          command: ["/cloud_sql_proxy", "--dir=/cloudsql",
                    "-instances=abcxyz:europe-west1:wordpressdb2=tcp:3306",
                    "-credential_file=/secrets/cloudsql/credentials.json"]
          volumeMounts:
            - name: cloudsql-instance-credentials
              mountPath: /secrets/cloudsql
              readOnly: true
            - name: ssl-certs
              mountPath: /etc/ssl/certs
            - name: cloudsql
              mountPath: /cloudsql
      volumes:
        - name: wordpress-persistent-storage
          persistentVolumeClaim:
            claimName: "task-pv-claim"
        - name: cloudsql-instance-credentials
          secret:
            secretName: cloudsql-instance-credentials
        - name: ssl-certs
          hostPath:
            path: /etc/ssl/certs
        - name: cloudsql
          emptyDir:

pVolume.yaml

apiVersion: "v1"
kind: "PersistentVolume"
metadata:
  name: "pv0001" 
spec:
  storageClassName: manual
  capacity:
    storage: "10Gi" 
  accessModes:
    - "ReadWriteMany"
  gcePersistentDisk: 
    fsType: "ext4" 
    pdName: "wordpress-disk"

pVolumeClaim.yaml

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: task-pv-claim
spec:
  storageClassName: manual
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 3Gi

Answer 1

持久性卷声明的spec.accessModes必须与持久卷中的spec.selector匹配。尝试将它们更改为相同的值。

如果这不起作用，您可以将metadata.labels定义添加到持久性卷声明定义中，方法是将其更新为与您的持久卷apiVersion: "v1" kind: "PersistentVolume" metadata: name: "pv0001" labels: name: "pv0001" # can be anything as long as it matches the selector in the pvc spec: ... ---- kind: PersistentVolumeClaim apiVersion: v1 metadata: name: task-pv-claim spec: storageClassName: manual accessModes: - ReadWriteOnce resources: requests: storage: 3Gi selector: matchLabels: name: "pv0001"匹配，如下所示：

spec.selector

{{1}}用作过滤器，以确保只匹配具有指定标签的PV。

Kubernetes没有声称持续量 - “由于PersistentVolumeClaim未被约束而失败：”task-pv-claim“，这是出乎意料的。”

1 个答案: