How can I get OpenEBS jiva working in a multi-node microk8s cluster using the OpenEBS community add-on? #3603

brentgroves · 2023-01-13T23:57:13Z

brentgroves
Jan 13, 2023

I have tried all sorts of things to get OpenEBS jiva to work on microk8s without much success. So rather than give up completely I thought I would detail one of my failed attempts and see if anyone could figure out what I am doing wrong. Thanks in advance for any help you can give me :-)

The issue
I think the reason openebs-jiva is not working is because the registered replica are less than 3.

view the cas controller log

kubectl logs -f deployment.apps/pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-ctrl -n openebs

time="2023-01-14T18:11:00Z" level=info msg="Register Replica, Address: 10.1.216.73 UUID: 98af9e7ae85fe048409f434d06fa42c311e74800 Uptime: 18h57m15.023468826s State: closed Type: Backend RevisionCount: 1"
time="2023-01-14T18:11:00Z" level=warning msg="No of yet to be registered replicas are less than 3 , No of registered replicas: 1"
...

Attempt
Here is the results of following the steps posted on at https://microk8s.io/docs/addon-openebs as well as the prerequisites found at https://openebs.io/docs/user-guides/installation
VM Setup:
3 VM running Ubuntu 22.04 with 16GB ram using VMware's vSphere. I have used these same VM to create a 3 node microk8s cluster with good success in the past.
Microk8s fresh install:
In this attempt I would like to try the edge channel to see if there is any recent bug fixes that would help jiva to work on microk8s.
https://microk8s.io/docs/setting-snap-channel
snap info microk8s
On all 3 nodes:

sudo snap install microk8s --classic --channel=1.26/edge

verify everything is ok

microk8s status  
microk8s inspect  
**Do what inspect tells you to do:**  
WARNING:  IPtables FORWARD policy is DROP. Consider enabling traffic forwarding with: sudo iptables -P FORWARD ACCEPT 
The change can be made persistent with: sudo apt-get install iptables-persistent  
sudo iptables -S  
sudo iptables-legacy -S  
sudo iptables -P FORWARD ACCEPT  
sudo apt-get install iptables-persistent  
sudo systemctl is-enabled netfilter-persistent.service  
sudo reboot  
microk8s inspect

still get the IPtable FORWARD warning on 2 of the 3 nodes.
iptables-legacy -S says FORWARD ACCEPT but iptables -S always reverts back to DROP. Hopefully it is not that important.
ping all the ip addresses in cluster from every node.
The reason I ping all the ip addresses is because of a warning I got about having more than 3 DNS servers configured.

cat /run/systemd/resolve/resolv.conf
nameserver 10.1.2.69
nameserver 10.1.2.70
nameserver 172.10.0.39
# Too many DNS servers configured, the following entries may be ignored.
nameserver 10.30.1.27
search .

Followed the directions at https://openebs.io/docs/user-guides/jiva/jiva-prerequisites
Did the following on all 3 nodes:


sudo apt install open-iscsi
sudo systemctl enable --now iscsid
sudo modprobe iscsi_tcp
sudo touch /etc/modules-load.d/iscsi-tcp.conf
sudo chmod 666 /etc/modules-load.d/iscsi-tcp.conf
echo iscsi_tcp >/etc/modules-load.d/iscsi-tcp.conf
cat /etc/modules-load.d/iscsi-tcp.conf
sudo reboot
sudo systemctl status iscsid.service

● iscsid.service - iSCSI initiator daemon (iscsid)
     Loaded: loaded (/lib/systemd/system/iscsid.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2023-01-13 15:27:15 EST; 5min ago
TriggeredBy: ● iscsid.socket
       Docs: man:iscsid(8)
    Process: 1374 ExecStartPre=/lib/open-iscsi/startup-checks.sh (code=exited, status=0/SUCCESS)
    Process: 1379 ExecStart=/sbin/iscsid (code=exited, status=0/SUCCESS)
   Main PID: 1383 (iscsid)
      Tasks: 2 (limit: 19118)
     Memory: 5.5M
        CPU: 363ms
     CGroup: /system.slice/iscsid.service
             ├─1382 /sbin/iscsid
             └─1383 /sbin/iscsid

Jan 13 15:27:14 reports01 systemd[1]: Starting iSCSI initiator daemon (iscsid)...
Jan 13 15:27:15 reports01 iscsid[1379]: iSCSI logger with pid=1382 started!
Jan 13 15:27:15 reports01 iscsid[1382]: iSCSI daemon with pid=1383 started!
Jan 13 15:27:15 reports01 systemd[1]: Started iSCSI initiator daemon (iscsid).

Create 3 node cluster.
Followed the directions at https://microk8s.io/docs/addon-openebs
step 1:

microk8s enable community
microk8s enable openebs
Infer repository community for addon openebs
Infer repository core for addon dns
Enabling DNS
Using host configuration from /run/systemd/resolve/resolv.conf
Applying manifest
serviceaccount/coredns created
configmap/coredns created
deployment.apps/coredns created
service/kube-dns created
clusterrole.rbac.authorization.k8s.io/coredns created
clusterrolebinding.rbac.authorization.k8s.io/coredns created
Restarting kubelet
Adding argument --cluster-domain to nodes.
Adding argument --cluster-dns to nodes.
Restarting nodes.
DNS is enabled
Infer repository core for addon helm3
Addon core/helm3 is already enabled
"openebs" already exists with the same configuration, skipping
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "openebs-jiva" chart repository
...Successfully got an update from the "openebs" chart repository
Update Complete. ⎈Happy Helming!⎈
NAME: openebs
LAST DEPLOYED: Fri Jan 13 16:03:08 2023
NAMESPACE: openebs
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Successfully installed OpenEBS.

step 2: check status

kubectl get all -n openebs
NAME                                                 READY   STATUS    RESTARTS      AGE
pod/openebs-ndm-8mllj                                1/1     Running   0             47m
pod/openebs-ndm-zjkfs                                1/1     Running   0             47m
pod/openebs-ndm-qz9s7                                1/1     Running   0             47m
pod/openebs-cstor-admission-server-f5d57f788-s86lf   1/1     Running   0             47m
pod/openebs-cstor-csi-node-t7jf5                     2/2     Running   0             47m
pod/openebs-cstor-cspc-operator-7dd775b4b8-7jjwx     1/1     Running   0             47m
pod/openebs-cstor-csi-node-pjbxw                     2/2     Running   0             47m
pod/openebs-cstor-csi-node-k4l2j                     2/2     Running   0             47m
pod/openebs-jiva-csi-node-g42g6                      3/3     Running   0             47m
pod/openebs-cstor-cvc-operator-7946b467f5-pwkgr      1/1     Running   0             47m
pod/openebs-ndm-operator-74fc47c6cc-c74lb            1/1     Running   1 (44m ago)   47m
pod/openebs-jiva-csi-node-kks56                      3/3     Running   1 (44m ago)   47m
pod/openebs-jiva-operator-594fdd69b9-rj2mb           1/1     Running   0             47m
pod/openebs-jiva-csi-controller-0                    5/5     Running   0             47m
pod/openebs-jiva-csi-node-gtnhw                      3/3     Running   0             47m
pod/openebs-cstor-csi-controller-0                   6/6     Running   0             47m
pod/openebs-localpv-provisioner-99449bb55-56csp      1/1     Running   4 (40m ago)   47m

NAME                                     TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
service/openebs-cstor-cvc-operator-svc   ClusterIP   10.152.183.134   <none>        5757/TCP   48m
service/openebs-cstor-admission-server   ClusterIP   10.152.183.47    <none>        443/TCP    45m

NAME                                    DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/openebs-ndm              3         3         3       3            3           <none>          48m
daemonset.apps/openebs-cstor-csi-node   3         3         3       3            3           <none>          48m
daemonset.apps/openebs-jiva-csi-node    3         3         3       3            3           <none>          48m

NAME                                             READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/openebs-cstor-admission-server   1/1     1            1           48m
deployment.apps/openebs-cstor-cspc-operator      1/1     1            1           48m
deployment.apps/openebs-cstor-cvc-operator       1/1     1            1           48m
deployment.apps/openebs-ndm-operator             1/1     1            1           48m
deployment.apps/openebs-jiva-operator            1/1     1            1           48m
deployment.apps/openebs-localpv-provisioner      1/1     1            1           48m

NAME                                                       DESIRED   CURRENT   READY   AGE
replicaset.apps/openebs-cstor-admission-server-f5d57f788   1         1         1       47m
replicaset.apps/openebs-cstor-cspc-operator-7dd775b4b8     1         1         1       47m
replicaset.apps/openebs-cstor-cvc-operator-7946b467f5      1         1         1       47m
replicaset.apps/openebs-ndm-operator-74fc47c6cc            1         1         1       47m
replicaset.apps/openebs-jiva-operator-594fdd69b9           1         1         1       47m
replicaset.apps/openebs-localpv-provisioner-99449bb55      1         1         1       47m

NAME                                            READY   AGE
statefulset.apps/openebs-jiva-csi-controller    1/1     48m
statefulset.apps/openebs-cstor-csi-controller   1/1     48m

step 3: verify storage class was installed

kubectl get sc
NAME                       PROVISIONER           RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
openebs-device             openebs.io/local      Delete          WaitForFirstConsumer   false                  64m
openebs-jiva-csi-default   jiva.csi.openebs.io   Delete          Immediate              true                   64m
openebs-hostpath           openebs.io/local      Delete          WaitForFirstConsumer   false                  64m

Now test openebs-jiva volume claim

cat <<EOF | microk8s kubectl apply -f -
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: busybox-jiva-pvc
spec:
  storageClassName: openebs-jiva-csi-default
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5G%
EOF

kubectl describe pvc busybox-jiva-pvc
Name:          busybox-jiva-pvc
Namespace:     default
StorageClass:  openebs-jiva-csi-default
Status:        Bound
Volume:        pvc-f8d287df-0a77-4958-8e57-da5f81921c9d
Labels:        <none>
Annotations:   pv.kubernetes.io/bind-completed: yes
               pv.kubernetes.io/bound-by-controller: yes
               volume.beta.kubernetes.io/storage-provisioner: jiva.csi.openebs.io
               volume.kubernetes.io/storage-provisioner: jiva.csi.openebs.io
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      5G
Access Modes:  RWO
VolumeMode:    Filesystem
Used By:       <none>
Events:
  Type    Reason                 Age                From                                                                                    Message
  ----    ------                 ----               ----                                                                                    -------
  Normal  ExternalProvisioning   73s (x2 over 73s)  persistentvolume-controller                                                             waiting for a volume to be created, either by external provisioner "jiva.csi.openebs.io" or manually created by system administrator
  Normal  Provisioning           73s                jiva.csi.openebs.io_openebs-jiva-csi-controller-0_afd2c95f-03a5-4349-b1bc-0e72dd421068  External provisioner is provisioning volume for claim "default/busybox-jiva-pvc"
  Normal  ProvisioningSucceeded  72s                jiva.csi.openebs.io_openebs-jiva-csi-controller-0_afd2c95f-03a5-4349-b1bc-0e72dd421068  Successfully provisioned volume pvc-f8d287df-0a77-4958-8e57-da5f81921c9d

Has any additional pods,service,deployments,stateful sets been created.

kubectl get all -n openebs

NAME                                                                  READY   STATUS             RESTARTS        AGE
pod/openebs-ndm-8mllj                                                 1/1     Running            0               133m
pod/openebs-ndm-zjkfs                                                 1/1     Running            0               133m
pod/openebs-ndm-qz9s7                                                 1/1     Running            0               133m
pod/openebs-cstor-admission-server-f5d57f788-s86lf                    1/1     Running            0               133m
pod/openebs-cstor-csi-node-t7jf5                                      2/2     Running            0               133m
pod/openebs-cstor-cspc-operator-7dd775b4b8-7jjwx                      1/1     Running            0               133m
pod/openebs-cstor-csi-node-pjbxw                                      2/2     Running            0               133m
pod/openebs-cstor-csi-node-k4l2j                                      2/2     Running            0               133m
pod/openebs-jiva-csi-node-g42g6                                       3/3     Running            0               133m
pod/openebs-cstor-cvc-operator-7946b467f5-pwkgr                       1/1     Running            0               133m
pod/openebs-ndm-operator-74fc47c6cc-c74lb                             1/1     Running            1 (130m ago)    133m
pod/openebs-jiva-csi-node-kks56                                       3/3     Running            1 (130m ago)    133m
pod/openebs-jiva-operator-594fdd69b9-rj2mb                            1/1     Running            0               133m
pod/openebs-jiva-csi-controller-0                                     5/5     Running            0               133m
pod/openebs-jiva-csi-node-gtnhw                                       3/3     Running            0               133m
pod/openebs-cstor-csi-controller-0                                    6/6     Running            0               133m
pod/pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-ctrl-68547ffnxtf5   2/2     Running            0               8m20s
pod/pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-rep-0               1/1     Running            2 (4m41s ago)   8m18s
pod/pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-rep-1               1/1     Running            3 (4m3s ago)    8m18s
pod/openebs-localpv-provisioner-99449bb55-56csp                       1/1     Running            7 (3m11s ago)   133m
pod/pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-rep-2               0/1     CrashLoopBackOff   3 (45s ago)     8m17s

NAME                                                             TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE
service/openebs-cstor-cvc-operator-svc                           ClusterIP   10.152.183.134   <none>        5757/TCP                     134m
service/openebs-cstor-admission-server                           ClusterIP   10.152.183.47    <none>        443/TCP                      131m
service/pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-ctrl-svc   ClusterIP   10.152.183.123   <none>        3260/TCP,9501/TCP,9500/TCP   8m22s

NAME                                    DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/openebs-ndm              3         3         3       3            3           <none>          134m
daemonset.apps/openebs-cstor-csi-node   3         3         3       3            3           <none>          134m
daemonset.apps/openebs-jiva-csi-node    3         3         3       3            3           <none>          134m

NAME                                                                 READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/openebs-cstor-admission-server                       1/1     1            1           134m
deployment.apps/openebs-cstor-cspc-operator                          1/1     1            1           134m
deployment.apps/openebs-cstor-cvc-operator                           1/1     1            1           134m
deployment.apps/openebs-ndm-operator                                 1/1     1            1           134m
deployment.apps/openebs-jiva-operator                                1/1     1            1           134m
deployment.apps/pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-ctrl   1/1     1            1           8m20s
deployment.apps/openebs-localpv-provisioner                          1/1     1            1           134m

NAME                                                                            DESIRED   CURRENT   READY   AGE
replicaset.apps/openebs-cstor-admission-server-f5d57f788                        1         1         1       133m
replicaset.apps/openebs-cstor-cspc-operator-7dd775b4b8                          1         1         1       133m
replicaset.apps/openebs-cstor-cvc-operator-7946b467f5                           1         1         1       133m
replicaset.apps/openebs-ndm-operator-74fc47c6cc                                 1         1         1       133m
replicaset.apps/openebs-jiva-operator-594fdd69b9                                1         1         1       133m
replicaset.apps/pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-ctrl-68547ff44c   1         1         1       8m20s
replicaset.apps/openebs-localpv-provisioner-99449bb55                           1         1         1       133m

NAME                                                                 READY   AGE
statefulset.apps/openebs-jiva-csi-controller                         1/1     134m
statefulset.apps/openebs-cstor-csi-controller                        1/1     134m
statefulset.apps/pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-rep   2/3     8m20s

yes they have.
Check the logs

These 2 look ok.
kubectl logs -n openebs daemonset.apps/openebs-jiva-csi-node
kubectl logs -n openebs daemonset.apps/openebs-cstor-csi-node

This looks questionable:
kubectl logs -n openebs daemonset.apps/openebs-ndm | grep error
I hope these errors mean something to someone:
Found 3 pods, using pod/openebs-ndm-8mllj
E0113 21:04:27.273861       6 osdiskexcludefilter.go:92] unable to configure os disk filter for mountpoint: /etc/hosts, error: could not get device mount attributes, Path/MountPoint not present in mounts file
E0113 21:04:27.274836       6 osdiskexcludefilter.go:92] unable to configure os disk filter for mountpoint: /boot, error: could not get device mount attributes, Path/MountPoint not present in mounts file
E0113 21:04:27.275644       6 osdiskexcludefilter.go:104] unable to configure os disk filter for mountpoint: /, error: could not get device mount attributes, Path/MountPoint not present in mounts file
E0113 21:04:27.276899       6 osdiskexcludefilter.go:104] unable to configure os disk filter for mountpoint: /boot, error: could not get device mount attributes, Path/MountPoint not present in mounts file
E0113 21:04:27.549116       6 usedbyprobe.go:160] error reading spdk signature from device: /dev/sda2, error reading from /dev/sda2: unexpected EOF
E0113 21:04:27.569473       6 smartprobe.go:101] map[errorCheckingConditions:the device type is not supported yet, device type: "unknown"]
E0113 21:04:28.472481       6 usedbyprobe.go:160] error reading spdk signature from device: /dev/loop2, error reading from /dev/loop2: unexpected EOF
E0113 21:04:28.473777       6 smartprobe.go:101] map[errorCheckingConditions:the device type is not supported yet, device type: "unknown"]
E0113 21:04:28.831109       6 usedbyprobe.go:160] error reading spdk signature from device: /dev/loop30, error reading from /dev/loop30: EOF
E0113 21:04:28.833587       6 smartprobe.go:101] map[errorCheckingConditions:the device type is not supported yet, device type: "unknown"]

Check the IP address of the pods that show a CrashLoopBackOff again.

kubectl get pods -n openebs -o wide
pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-ctrl-68547ffnxtf5   2/2     Running            0               33m    10.1.216.71    reports03   <none>           <none>
pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-rep-0               1/1     Running            2 (29m ago)     33m    10.1.216.73    reports03   <none>           <none>
openebs-localpv-provisioner-99449bb55-56csp                       1/1     Running            7 (28m ago)     158m   10.1.216.69    reports03   <none>           <none>
pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-rep-2               0/1     CrashLoopBackOff   6 (3m35s ago)   33m    10.1.197.7     reports02   <none>           <none>
pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-rep-1               0/1     CrashLoopBackOff   6 (34s ago)     33m    10.1.120.198   reports01   <none>           <none>

noticed the reports03 node seems to be running ok.
take a look at the pvc

kubectl get pvc 
NAME                   STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS               AGE
busybox-jiva-pvc       Bound    pvc-f8d287df-0a77-4958-8e57-da5f81921c9d   5G         RWO            openebs-jiva-csi-default   38m

kubectl describe pvc busybox-jiva-pvc
Name:          busybox-jiva-pvc
Namespace:     default
StorageClass:  openebs-jiva-csi-default
Status:        Bound
Volume:        pvc-f8d287df-0a77-4958-8e57-da5f81921c9d
Labels:        <none>
Annotations:   pv.kubernetes.io/bind-completed: yes
               pv.kubernetes.io/bound-by-controller: yes
               volume.beta.kubernetes.io/storage-provisioner: jiva.csi.openebs.io
               volume.kubernetes.io/storage-provisioner: jiva.csi.openebs.io
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      5G
Access Modes:  RWO
VolumeMode:    Filesystem
Used By:       <none>
Events:        <none>

kubectl get jivavolume pvc-f8d287df-0a77-4958-8e57-da5f81921c9d -n openebs
NAME                                       REPLICACOUNT   PHASE     STATUS
pvc-f8d287df-0a77-4958-8e57-da5f81921c9d                  Syncing   RO

view the cas controller log

kubectl logs -f deployment.apps/pvc-f8d287df-0a77-4958-8e57-da5f81921c9d-jiva-ctrl -n openebs

time="2023-01-14T18:11:00Z" level=info msg="Register Replica, Address: 10.1.216.73 UUID: 98af9e7ae85fe048409f434d06fa42c311e74800 Uptime: 18h57m15.023468826s State: closed Type: Backend RevisionCount: 1"
time="2023-01-14T18:11:00Z" level=warning msg="No of yet to be registered replicas are less than 3 , No of registered replicas: 1"
...

Answered by brentgroves

Jan 24, 2023

The issue
I think the reason openebs-jiva is not working is only 1 ndm,cstor-csi, and jiva-csi pod expected 3 of each.
(base) brent@reports41  ~  kubectl get all -n openebs
NAME READY STATUS RESTARTS AGE
pod/openebs-ndm-lfr9m 1/1 Running 0 103m
pod/openebs-jiva-operator-594fdd69b9-6gtck 1/1 Running 0 103m
pod/openebs-cstor-cvc-operator-7946b467f5-jdkpx 1/1 Running 0 103m
pod/openebs-cstor-admission-server-f5d57f788-qsmzs 1/1 Running 0 103m
pod/openebs-ndm-operator-74fc47c6cc-c5b74 1/1 Running 0 103m
pod/openebs-localpv-provisioner-99449bb55-zqn7r 1/1 Running 0 103m
pod/openebs-cstor-cspc-operator-7dd775b4b8-26kh7 1/1 Running 0 103m
pod/openebs-cstor-csi-node-t9n2l 2/2 Running 0 103m
pod…

View full answer

brentgroves · 2023-01-24T00:09:45Z

brentgroves
Jan 24, 2023
Author

The issue
I think the reason openebs-jiva is not working is only 1 ndm,cstor-csi, and jiva-csi pod expected 3 of each.
(base) brent@reports41  ~  kubectl get all -n openebs
NAME READY STATUS RESTARTS AGE
pod/openebs-ndm-lfr9m 1/1 Running 0 103m
pod/openebs-jiva-operator-594fdd69b9-6gtck 1/1 Running 0 103m
pod/openebs-cstor-cvc-operator-7946b467f5-jdkpx 1/1 Running 0 103m
pod/openebs-cstor-admission-server-f5d57f788-qsmzs 1/1 Running 0 103m
pod/openebs-ndm-operator-74fc47c6cc-c5b74 1/1 Running 0 103m
pod/openebs-localpv-provisioner-99449bb55-zqn7r 1/1 Running 0 103m
pod/openebs-cstor-cspc-operator-7dd775b4b8-26kh7 1/1 Running 0 103m
pod/openebs-cstor-csi-node-t9n2l 2/2 Running 0 103m
pod/openebs-jiva-csi-node-hl268 3/3 Running 0 103m
pod/openebs-cstor-csi-controller-0 6/6 Running 0 103m
pod/openebs-jiva-csi-controller-0 5/5 Running 0 103m

0 replies

avishnu · 2024-01-21T13:56:56Z

avishnu
Jan 21, 2024
Maintainer

Jiva and CStor are now legacy replicated engines. Please move to Mayastor as this is the latest, stable and most active replicated engine from OpenEBS portfolio.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

OpenEBS

How can I get OpenEBS jiva working in a multi-node microk8s cluster using the OpenEBS community add-on? #3603

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

OpenEBS

How can I get OpenEBS jiva working in a multi-node microk8s cluster using the OpenEBS community add-on? #3603

brentgroves Jan 13, 2023

Replies: 2 comments

brentgroves Jan 24, 2023 Author

avishnu Jan 21, 2024 Maintainer

brentgroves
Jan 13, 2023

brentgroves
Jan 24, 2023
Author

avishnu
Jan 21, 2024
Maintainer