microk8s-hostpath 不会为声明创建 PV答案

【问题标题】：microk8s-hostpath does not create PV for a claimmicrok8s-hostpath 不会为声明创建 PV
【发布时间】：2021-06-19 06:17:16
【问题描述】：

我正在尝试使用 Microk8s 存储插件，但我的 PVC 和 pod 卡在待处理状态，我不知道出了什么问题。我还使用了“注册表”插件，它使用了存储并且可以正常工作。

仅供参考：我已经多次重启了microk8s，甚至完全删除并重新安装了它，但问题仍然存在。

Yaml 文件：

# =================== pvc.yaml
apiVersion: v1
kind: List
items:
- apiVersion: v1
  kind: PersistentVolumeClaim
  metadata:
    name: wws-registry-claim
  spec:
    volumeName: registry-pvc
    accessModes:
      - ReadWriteOnce
    resources:
      requests:
        storage: 1Gi
    storageClassName: microk8s-hostpath

# =================== deployment.yaml (just spec section)
spec:
  serviceName: registry
  replicas: 1
  selector:
    matchLabels:
      io.kompose.service: registry
  template:
    metadata:
      labels:
        io.kompose.service: registry
    spec:
      containers:
      - image: {{ .Values.image }}
        name: registry-master
        ports:
        - containerPort: 28015
        - containerPort: 29015
        - containerPort: 8080
        resources:
          requests:
            cpu: {{ .Values.request_cpu }}
            memory: {{ .Values.request_memory }}
          limits:
            cpu: {{ .Values.limit_cpu }}
            memory: {{ .Values.limit_memory }}
        volumeMounts:
        - mountPath: /data
          name: rdb-local-data
        env:
        - name: RUN_ENV
          value: 'kubernetes'
        - name: MY_POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: MY_POD_IP
          valueFrom:
            fieldRef:
              fieldPath: status.podIP
      volumes:
      - name: rdb-local-data
        persistentVolumeClaim:
          claimName: wws-registry-claim

集群信息：

$ kubectl get pvc -A
NAMESPACE            NAME                 STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS        AGE
container-registry   registry-claim       Bound     pvc-dfef8e65-0618-4980-8b3c-e6e9efc5b0ca   20Gi       RWX            microk8s-hostpath   56m
default              wws-registry-claim   Pending   registry-pvc                               0                         microk8s-hostpath   23m


$ kubectl get pv -A
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                               STORAGECLASS        REASON   AGE
pvc-dfef8e65-0618-4980-8b3c-e6e9efc5b0ca   20Gi       RWX            Delete           Bound    container-registry/registry-claim   microk8s-hostpath            56m


$ kubectl get pods -n kube-system 
NAME                                    READY   STATUS    RESTARTS   AGE
coredns-9b8997588-vk5vt                 1/1     Running   0          57m
hostpath-provisioner-7b9cb5cdb4-wxcp6   1/1     Running   0          57m
metrics-server-v0.2.1-598c8978c-74krr   2/2     Running   0          57m
tiller-deploy-77855d9dcf-4cvsv          1/1     Running   0          46m


$ kubectl -n kube-system logs hostpath-provisioner-7b9cb5cdb4-wxcp6 
I0322 12:31:31.231110       1 controller.go:293] Starting provisioner controller 87fc12df-8b0a-11eb-b910-ee8a00c41384!
I0322 12:31:31.231963       1 controller.go:893] scheduleOperation[lock-provision-container-registry/registry-claim[dfef8e65-0618-4980-8b3c-e6e9efc5b0ca]]
I0322 12:31:31.235618       1 leaderelection.go:154] attempting to acquire leader lease...
I0322 12:31:31.237785       1 leaderelection.go:176] successfully acquired lease to provision for pvc container-registry/registry-claim
I0322 12:31:31.237841       1 controller.go:893] scheduleOperation[provision-container-registry/registry-claim[dfef8e65-0618-4980-8b3c-e6e9efc5b0ca]]
I0322 12:31:31.239011       1 hostpath-provisioner.go:86] creating backing directory: /var/snap/microk8s/common/default-storage/container-registry-registry-claim-pvc-dfef8e65-0618-4980-8b3c-e6e9efc5b0ca
I0322 12:31:31.239102       1 controller.go:627] volume "pvc-dfef8e65-0618-4980-8b3c-e6e9efc5b0ca" for claim "container-registry/registry-claim" created
I0322 12:31:31.244798       1 controller.go:644] volume "pvc-dfef8e65-0618-4980-8b3c-e6e9efc5b0ca" for claim "container-registry/registry-claim" saved
I0322 12:31:31.244813       1 controller.go:680] volume "pvc-dfef8e65-0618-4980-8b3c-e6e9efc5b0ca" provisioned for claim "container-registry/registry-claim"
I0322 12:31:33.243345       1 leaderelection.go:196] stopped trying to renew lease to provision for pvc container-registry/registry-claim, task succeeded


$ kubectl get sc
NAME                PROVISIONER            AGE
microk8s-hostpath   microk8s.io/hostpath   169m


$ kubectl get sc -o yaml
apiVersion: v1
items:
- apiVersion: storage.k8s.io/v1
  kind: StorageClass
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"storage.k8s.io/v1","kind":"StorageClass","metadata":{"annotations":{},"name":"microk8s-hostpath"},"provisioner":"microk8s.io/hostpath"}
    creationTimestamp: "2021-03-22T12:31:25Z"
    name: microk8s-hostpath
    resourceVersion: "2845"
    selfLink: /apis/storage.k8s.io/v1/storageclasses/microk8s-hostpath
    uid: e94b5653-e261-4e1f-b646-e272e0c8c493
  provisioner: microk8s.io/hostpath
  reclaimPolicy: Delete
  volumeBindingMode: Immediate
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

Microk8s 检查：

$ microk8s.inspect 
Inspecting services
  Service snap.microk8s.daemon-cluster-agent is running
  Service snap.microk8s.daemon-flanneld is running
  Service snap.microk8s.daemon-containerd is running
  Service snap.microk8s.daemon-apiserver is running
  Service snap.microk8s.daemon-apiserver-kicker is running
  Service snap.microk8s.daemon-proxy is running
  Service snap.microk8s.daemon-kubelet is running
  Service snap.microk8s.daemon-scheduler is running
  Service snap.microk8s.daemon-controller-manager is running
  Service snap.microk8s.daemon-etcd is running
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
  Copy processes list to the final report tarball
  Copy snap list to the final report tarball
  Copy VM name (or none) to the final report tarball
  Copy disk usage information to the final report tarball
  Copy memory usage information to the final report tarball
  Copy server uptime to the final report tarball
  Copy current linux distribution to the final report tarball
  Copy openSSL information to the final report tarball
  Copy network configuration to the final report tarball
Inspecting kubernetes cluster
  Inspect kubernetes cluster

WARNING:  Docker is installed. 
Add the following lines to /etc/docker/daemon.json: 
{
    "insecure-registries" : ["localhost:32000"] 
}
and then restart docker with: sudo systemctl restart docker
Building the report tarball
  Report tarball is at /var/snap/microk8s/1671/inspection-report-20210322_143034.tar.gz

【问题讨论】：

kubectl get sc 输出的 o/p 是什么？
我更新了我的问题并在“集群信息”部分的末尾添加了输出。
可能，在您的pvc 存储类中使用的是storageClassName: mk8s-sc 但k get sc 只显示`microk8s-hostpath。为什么这种不匹配？
感谢您注意到不匹配，我对其进行了更改，删除了所有内容并重新启动它们，但它仍然处于等待状态，没有错误或新登录 hostpath-provisioner。不匹配的原因是：起初我创建了自己的sc，但后来我发现当我启用storage addson 时，Microk8s 会为我创建一个。
你检查了stackoverflow.com/a/60213860/6309601和stackoverflow.com/a/55982035/6309601

标签： kubernetes persistent kubernetes-pvc microk8s

【解决方案1】：

我发现了问题。由于“host-provisioner”负责创建 PV，我们不应在 PVC yaml 文件中传递volumeName。当我删除该字段时，provisioner 可以创建一个 PV 并将我的 PVC 绑定到它，现在我的 pod 已经启动。

现在我的 PVC 是：

apiVersion: v1
kind: List
items:
- apiVersion: v1
  kind: PersistentVolumeClaim
  metadata:
    name: wws-registry-claim
  spec:
    # volumeName: registry-pvc
    accessModes:
      - ReadWriteOnce
    resources:
      requests:
        storage: 1Gi
    storageClassName: microk8s-hostpath

【讨论】：