In this post, I would like to share how I was able to run Jira Data Center on Kubernetes in an effect way.
First of all, you need to have a storage class that supports dynamic provisioning. If you don’t have one, you can create one by following this how to articles: Use Glusterfs for Dynamic Volume Provisioning in Kubernetes. In this example, I use Glusterfs for my persistent data.
Second of all, you need to have a database ready. If not, you can quickly setup one on Kubernetes as well. I have the example for creating Postgres:
By now, we should have all prerequisites (dynamic PV and database) ready. Lets start to build Jira Data Center.
Jira Data Center needs two home folders: One is local home folder, the other one is shared home folder. They both need to be stored on persistent volume, as pods are short living, but the data needs to stay permanently.
Step one: create a persistent volume for the shared home. As we use dynamic persistent volume provisioning, we only need to create a PVC (persistent volume claim), the PV (persistent volume) will be created on the fly.
Step two: create a config map which will be used to pass the environment variables into the containers. Adjust the settings accordingly. In the example, we use the official Jira Software docker images
Step three: create statefulSet for Jira. As Jira cluster is a stateful application, here statefulSet fits better than deployment. e.g statefulSet supports ordinal startup and shutdown. The jira local home folder is created dynamically here, and it is tied to a specific pod based on the pod’s name. e.g jira-0, jira-1 …
Step four: create a service for Jira. You can either do NodePort or ClusterIP. If you have ingress controller, then ClusterIP should just be fine. In my case, I use traefik to route the traffics to Jira service if the hostname is jira-sande.mydomain.com.
80% of the work should be done by now. The rest are just some configurations which I will show you in the part 2.