Release highlights (CHANGELOG)
- Improved documentation. (Thanks to @papanito)
- Enhanced to handle invalid Pod names when k8s node name is used as part of pod name.
- Added more test cases to cover Replica 3 Volume use cases.
- Fixed a crash during Gluster volume mount in CSI pods.
- The operator is enhanced to start self heal daemon when Replica 3 volume is created.
Usage
Deploy KaDalu Operator on an already running Kubernetes cluster using,
kubectl create -f https://raw.githubusercontent.com/kadalu/kadalu/master/manifests/kadalu-operator-0.3.0.yaml
Use kadalu-operator-openshift-0.3.0.yaml
in case of Openshift.
oc create -f https://raw.githubusercontent.com/kadalu/kadalu/master/manifests/kadalu-operator-openshift-0.3.0.yaml
KaDalu Operator listens to Storage setup configuration changes and starts the required pods. For example,
# File: storage-config.yaml
---
apiVersion: kadalu-operator.storage/v1alpha1
kind: KadaluStorage
metadata:
# This will be used as the name of PV Hosting Volume
name: storage-pool-1
spec:
type: Replica1
storage:
- node: kube1 # node name as shown in `kubectl get nodes`
device: /dev/vdc # Device to provide storage to all PVs
Now request kadalu-operator to setup storage using,
$ kubectl create -f storage-config.yaml
Operator will start the storage export pods as required. And, in 2 steps, your storage system is up and running.
Check the status of Pods using,
$ kubectl get pods -nkadalu
NAME READY STATUS RESTARTS AGE
server-storage-pool-1-kube1-0 1/1 Running 0 84s
csi-attacher-0 2/2 Running 0 30m
csi-nodeplugin-5hfms 2/2 Running 0 30m
csi-nodeplugin-924cc 2/2 Running 0 30m
csi-nodeplugin-cbjl9 2/2 Running 0 30m
csi-provisioner-0 3/3 Running 0 30m
operator-6dfb65dcdd-r664t 1/1 Running 0 30m
Run oc get pods -n kadalu
in case of Openshift.
For more information, please visit Kadalu GitHub page.