Persistent Volume Claims is Pending about consul-helm

[krancour]

If this happens to be on minikube, then this could be a duplicate of #13, which also mentions a workaround.

[kolesoffac]

If this happens to be on minikube, then this could be a duplicate of #13, which also mentions a workaround.

No, this to be on typical kubernetes cluster. It was install from scratch.

[krancour]

Sorry... I jumped the gun... the title of the PR looked so familiar to #13.

I'm looking more closely at your kubectl describe pvc and is says:

no persistent volumes available for this claim and no storage class is set

PersistentVolumeClaims must do one of three things:

1. Make a claim on an existing PV
2. Dynamically provision a new PV by making mention of the StorageClass that should be utilized in that process
3. Dynamically provision a new PV by relying on the cluster's default storage class.

By default, this chart utilizes situation no.3. But it would seem, perhaps, that your cluster does not actually have a default StorageClass defined.

What do you get when you do the following?

$ kubectl get storageclasses

[kolesoffac]

NAME                      PROVISIONER                    AGE
local-storage (default)   kubernetes.io/no-provisioner   129m

I add this manually sc local-storage:

{
  "kind": "StorageClass",
  "apiVersion": "storage.k8s.io/v1",
  "metadata": {
    "name": "local-storage",
    "annotations": {
      "storageclass.kubernetes.io/is-default-class": "true"
    }
  },
  "provisioner": "kubernetes.io/no-provisioner",
  "reclaimPolicy": "Delete",
  "volumeBindingMode": "WaitForFirstConsumer"
}

[krancour]

Do you have any better luck if you install / upgrade the chart with --set server.storageClass=local-storage?

Have you tried to manually define a PVC that uses that storage class to verify it works?

[kolesoffac]

Do you have any better luck if you install / upgrade the chart with --set server.storageClass=local-storage?

Already try with same result pending.

Have you tried to manually define a PVC that uses that storage class to verify it works?

I complete this. And this is work.

Why dont auto create new pv for consul pods?

[adilyse]

It looks like the type of storage you are using is the limiting factor in this case. The StatefulSet will try to create the persistent volumes, but this only works with StorageClass types that are able to be dynamically provisioned. The Local storage type doesn't meet this requirement.

I've added some information to the docs to make this requirement more clear. Hope that helps!