We are looking into moving our Jira instance on a Kubernetes cluster and one of the concerns that were recently risen is whether we should go with a StatefulSet or a Deployment. So, are there any suggestions or lessons learned by using any of the above controllers?
Any additional tips, source of information and comments by people who went through the process could be very valuable to us.
Jira is a stateful monolith. You should very much so use a v1/Statefulset. Check this out.
https://github.com/Bonn93/atlassian-kubernetes/tree/master/jira
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1、helm test chot-jira-dev -n jira --debug (without network)
Any help would be appreciated. 3Q
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@王九日 it doesn't look like Jira has started correctly. Test pod just runs curl to verify status and expects it to be FIRST_RUN or RUNNING. Sharing Jira pod logs may shed some light on what is happening.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Has anyone been able to get Jira to run in Kubernetes successfully using the Atlassian images? I can get it to kind of work but it takes 15+ minutes to start up and plugins fail to load. I have it running on a beefy K8S nodes but the pod never seem to want to use more then 100-200m cpu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This sounds like an issue with Jira & the plugins. Analyzing and exploring Jira's logs would be the next course of action. Using my repo above and deploying several apps, scaling up and down on slow hardware takes between 3-5 minutes on a E5-2650L.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.