Wonder if this is a new DirectPV issue?
- Created my LVs as I use to:
ccelis@asus:~$ sudo truncate --size=1G /tmp/disk-{1..4}.img
for disk in /tmp/disk-{1..4}.img; do sudo losetup --find $disk; done
devices=( $(for disk in /tmp/disk-{1..4}.img; do sudo losetup --noheadings --output NAME --associated $disk; done) )
sudo pvcreate "${devices[@]}"
vgname="vg0"
sudo vgcreate "$vgname" "${devices[@]}"
for lvname in lv-{0..3}; do sudo lvcreate --name="$lvname" --size=800MiB "$vgname"; done
Physical volume "/dev/loop26" successfully created.
Physical volume "/dev/loop27" successfully created.
Physical volume "/dev/loop28" successfully created.
Physical volume "/dev/loop29" successfully created.
Volume group "vg0" successfully created
Logical volume "lv-0" created.
Logical volume "lv-1" created.
Logical volume "lv-2" created.
Logical volume "lv-3" created.- Started minikube to use those LVs:
ccelis@asus:~$ minikube start --driver=none
😄 minikube v1.26.1 on Ubuntu 22.04
✨ Using the none driver based on user configuration
👍 Starting control plane node minikube in cluster minikube
🤹 Running on localhost (CPUs=8, Memory=15697MB, Disk=959826MB) ...
ℹ️ OS release is Ubuntu 22.04.1 LTS
🐳 Preparing Kubernetes v1.24.3 on Docker 20.10.21 ...
▪ kubelet.resolv-conf=/run/systemd/resolve/resolv.conf
▪ Generating certificates and keys ...
▪ Booting up control plane ...
▪ Configuring RBAC rules ...
🤹 Configuring local host environment ...
❗ The 'none' driver is designed for experts who need to integrate with an existing VM
💡 Most users should use the newer 'docker' driver instead, which does not require root!
📘 For more information, see: https://minikube.sigs.k8s.io/docs/reference/drivers/none/
❗ kubectl and minikube configuration will be stored in /home/ccelis
❗ To use kubectl or minikube commands as your own user, you may need to relocate them. For example, to overwrite your own settings, run:
▪ sudo mv /home/ccelis/.kube /home/ccelis/.minikube $HOME
▪ sudo chown -R $USER $HOME/.kube $HOME/.minikube
💡 This can also be done automatically by setting the env var CHANGE_MINIKUBE_NONE_USER=true
🔎 Verifying Kubernetes components...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟 Enabled addons: default-storageclass, storage-provisioner
🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default- Installed plugin:
ccelis@asus:~$ kubectl krew install directpv
Updated the local copy of plugin index.
Installing plugin: directpv
Installed plugin: directpv
\
| Use this plugin:
| kubectl directpv
| Documentation:
| https://github.com/minio/directpv
/
WARNING: You installed plugin "directpv" from the krew-index plugin repository.
These plugins are not audited for security by the Krew maintainers.
Run them at your own risk.- Installed DirectPV:
ccelis@asus:~$ kubectl directpv install
I1214 13:08:02.552366 229809 ns.go:65] 'direct.csi.min.io' namespace created
I1214 13:08:02.561424 229809 rbac.go:352] 'direct.csi.min.io' rbac created
W1214 13:08:02.568857 229809 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
I1214 13:08:02.570651 229809 psp.go:128] 'direct.csi.min.io' podsecuritypolicy created
I1214 13:08:02.604796 229809 crd.go:135] crds successfully registered
I1214 13:08:02.619525 229809 csidriver.go:148] 'direct.csi.min.io' csidriver created
I1214 13:08:03.027851 229809 storageclass.go:48] 'direct.csi.min.io' storageclass created
I1214 13:08:03.036190 229809 service.go:38] 'direct.csi.min.io' service created
I1214 13:08:03.042590 229809 daemonset.go:41] 'direct.csi.min.io' daemonset created
I1214 13:08:03.052474 229809 deployment.go:289] 'direct.csi.min.io' deployment created- Getting pod issue:
ccelis@asus:~$ kubectl get pods -n direct-csi-min-io
NAME READY STATUS RESTARTS AGE
direct-csi-min-io-47546 3/4 Running 4 (24s ago) 111s
direct-csi-min-io-56bb74d49f-68tmg 0/2 Error 4 (23s ago) 111s
direct-csi-min-io-56bb74d49f-h7c6c 0/2 Error 4 (22s ago) 111s
direct-csi-min-io-56bb74d49f-mzb9c 0/2 Error 4 (21s ago) 111sccelis@asus:~$ kubectl logs direct-csi-min-io-56bb74d49f-68tmg -n direct-csi-min-io
Defaulted container "csi-provisioner" out of: csi-provisioner, direct-csi
W1214 18:10:13.543840 1 feature_gate.go:235] Setting GA feature gate Topology=true. It will be removed in a future release.
I1214 18:10:13.543864 1 feature_gate.go:243] feature gates: &{map[Topology:true]}
I1214 18:10:13.543873 1 csi-provisioner.go:138] Version: v2.2.0-go1.18
I1214 18:10:13.543876 1 csi-provisioner.go:161] Building kube configs for running in cluster...
F1214 18:10:43.545132 1 csi-provisioner.go:186] Error getting server version: Get "https://10.96.0.1:443/version?timeout=32s": dial tcp 10.96.0.1:443: i/o timeout
goroutine 1 [running]:
k8s.io/klog/v2.stacks(0x1)
/home/wlan0/code/go/src/github.com/kubernetes-csi/external-provisioner/vendor/k8s.io/klog/v2/klog.go:1021 +0x8a
k8s.io/klog/v2.(*loggingT).output(0x26deb40, 0x3, {0x0, 0x0}, 0xc0003bbce0, {0x1eddf7d?, 0x1?}, 0xc000081700?, 0x0)
/home/wlan0/code/go/src/github.com/kubernetes-csi/external-provisioner/vendor/k8s.io/klog/v2/klog.go:970 +0x569
k8s.io/klog/v2.(*loggingT).printf(0x6?, 0x4?, {0x0, 0x0}, {0x0, 0x0}, {0x18b3d22, 0x20}, {0xc000081700, 0x1, ...})
/home/wlan0/code/go/src/github.com/kubernetes-csi/external-provisioner/vendor/k8s.io/klog/v2/klog.go:751 +0x1d1
k8s.io/klog/v2.Fatalf(...)
/home/wlan0/code/go/src/github.com/kubernetes-csi/external-provisioner/vendor/k8s.io/klog/v2/klog.go:1509
main.main()
/home/wlan0/code/go/src/github.com/kubernetes-csi/external-provisioner/cmd/csi-provisioner/csi-provisioner.go:186 +0x9e5
goroutine 33 [chan receive]:
k8s.io/klog/v2.(*loggingT).flushDaemon(0xc000132000?)
/home/wlan0/code/go/src/github.com/kubernetes-csi/external-provisioner/vendor/k8s.io/klog/v2/klog.go:1164 +0x6a
created by k8s.io/klog/v2.init.0
/home/wlan0/code/go/src/github.com/kubernetes-csi/external-provisioner/vendor/k8s.io/klog/v2/klog.go:418 +0xf6
