Using OpenEBS as storage for Jira on Kubernetes

    Jira is a product designed to provide issue tracking and assist in moving tasks through the software development lifecycle. For this example we are leveraging a container image created by Kelsey Hightower. We will be creating a deployment and a service in this example.

    Requirements

    1. Install OpenEBS

      If OpenEBS is not installed in your K8s cluster, this can done from . If OpenEBS is already installed, go to the next step.

    2. Configure cStor Pool

    3. Create Storage Class

      You must configure a StorageClass to provision cStor volume on cStor pool. In this solution, we are using a StorageClass to consume the cStor Pool which is created using external disks attached on the Nodes. The storage pool is created using the steps provided in the Step 3. Since Jira is a deployment application, it requires three replication at the storage level. So cStor volume is 3. Sample YAML named openebs-sc-disk.yaml to consume cStor pool with cStor volume replica count as 3 is provided in the configuration details below.

    Next apply both the Jira deployment and service to your Kubernetes cluster. There is an example at the bottom of this guide for both.

    Verify Jira Pods

    Run the following to get the status of PostgreSQL pods.

    1. kubectl get pods

    openebs-config.yaml

    1. #Use the following YAMLs to create a cStor Storage Pool.
    2. # and associated storage class.
    3. apiVersion: openebs.io/v1alpha1
    4. kind: StoragePoolClaim
    5. metadata:
    6.   name: cstor-disk
    7. spec:
    8.   name: cstor-disk
    9.   type: disk
    10.   poolSpec:
    11.     poolType: striped
    12.   # NOTE - Appropriate disks need to be fetched using `kubectl get blockdevices -n openebs`
    13.   #
    14.   # `Block devices` is a custom resource supported by OpenEBS with `node-disk-manager`
    15.   # as the disk operator
    16. # Replace the following with actual disk CRs from your cluster `kubectl get blockdevices -n openebs`
    17. # Uncomment the below lines after updating the actual disk names.
    18.   blockDevices:
    19.     blockDeviceList:
    20. #   - blockdevice-69cdfd958dcce3025ed1ff02b936d9b4
    21. #   - blockdevice-891ad1b581591ae6b54a36b5526550a2
    22. #   - blockdevice-ceaab442d802ca6aae20c36d20859a0b
    24. ---

    openebs-sc-disk.yaml

    jira.yaml

    2. kind: Deployment
    3. metadata:
    4.   labels:
    5.     app: jira
    6.   name: jira
    7. spec:
    8.   replicas: 1
    9.   template:
    10.     metadata:
    11.       labels:
    12.         app: jira
    13.       name: jira
    14.     spec:
    15.       containers:
    16.         - name: jira
    17.           image: "doriftoshoes/jira:7.3.6"
    18.           resources:
    19.             requests:
    20.               cpu: "2"
    21.               memory: "2G"
    22.           volumeMounts:
    23.             - name: "jira-home"
    24.               mountPath: /opt/jira-home
    25.         - name: jira-home
    26.           persistentVolumeClaim:
    28. ---
    29. apiVersion: v1
    30. kind: Service
    31. metadata:
    32.   labels:
    33.     app: jira
    34.   name: jira
    35. spec:
    36.   ports:
    37.     - port: 8080
    38.       targetPort: 8080
    39.   selector:
    40.     app: jira
    41.   type: LoadBalancer
    42. ---
    43. kind: PersistentVolumeClaim
    44. apiVersion: v1
    45. metadata:
    46.   name: demo-vol1-claim
    47. spec:
    48.   storageClassName: openebs-cstor-disk
    49.   accessModes:
    50.     - ReadWriteOnce
    51.   resources:
    52.     requests:
    53.       storage: 10G

    Feedback

    Was this page helpful?

    Thanks for the feedback. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement. Engage and get additional help on .