I have seven kubernetes nodes, two of which are physical (bare metal) servers. One of these physical machines has a SSD I'd like to use as a portworx cache disk. Is this a supported configuration or will kubernetes endlessly look for that one disk on every host? Here's a snippet from the "spec" file I am using.
containers:
- name: portworx
image: portworx/oci-monitor:2.8.1.2
imagePullPolicy: Always
args:
["-k", "etcd:https://kube-kvdb.nppl.yo:2379", "-c", "px-nppl-00dZ16f4-1e2c-4afd-97fa-gf5aef26f24e", "-s", "/dev/vdb", "-cache", "/dev/sdb", "-secret_type", "k8s",
"-userpwd", "$PX_KVDB_USERNAME:$PX_KVDB_PASSWORD",
"-x", "kubernetes"]
And here is the state of my cluster.
msh@kube-kvdb:~$ kubectl get pods -n kube-system -o wide |grep port
portworx-5n9fx 1/2 Running 21 (8m39s ago) 5h36m 192.168.10.4 landrew <none> <none>
portworx-api-66z6c 0/1 Running 3 (158m ago) 5h36m 192.168.10.4 landrew <none> <none>
portworx-api-cx5k2 0/1 Running 1 (126m ago) 5h36m 192.168.10.35 kube1 <none> <none>
portworx-api-h6cj6 0/1 Running 42 (135m ago) 5h36m 192.168.10.36 kube2 <none> <none>
portworx-api-ngj9j 0/1 Running 0 5h36m 192.168.10.34 kube0 <none> <none>
portworx-api-zcdd8 0/1 Running 0 5h36m 192.168.10.37 kube3 <none> <none>
portworx-cnpt2 1/2 CrashLoopBackOff 74 (93s ago) 5h36m 192.168.10.35 kube1 <none> <none>
portworx-kj7vs 1/2 CrashLoopBackOff 114 (42s ago) 5h36m 192.168.10.36 kube2 <none> <none>
portworx-lf9l6 1/2 CrashLoopBackOff 69 (3m28s ago) 5h36m 192.168.10.34 kube0 <none> <none>
portworx-t6s4f 1/2 CrashLoopBackOff 69 (3m54s ago) 5h36m 192.168.10.37 kube3 <none> <none>
