Synchrony cluster failed to start with outbound proxy in AWS


If your synchrony cluster failed to start in AWS, the Collaborative Edit in Confluence will not work. And if your environment meet all the following criteria. Then I think you are in the right place. As I had the same issue, and finally figured it out that Synchrony has seperate JVM settings. The proxy settings … Continue reading Synchrony cluster failed to start with outbound proxy in AWS

Configure readinessProbe and livenessProbe for Jira Container on Kubernetes


The kubelet uses liveness probes to know when to restart a Container. For example, liveness probes could catch a deadlock, where an application is running, but unable to make progress. Restarting a Container in such a state can help to make the application more available despite bugs. The kubelet uses readiness probes to know when … Continue reading Configure readinessProbe and livenessProbe for Jira Container on Kubernetes

Configure Traefik Sticky Session in Kubernetes


As wrote earlier, I have a Jira Data Center cluster running on Kubernetes. The cluster has three nodes, and traefik is the ingress controller. https://gist.github.com/jc1518/9f1e0da8d61a865de9eef305d3cb20e2 Sometimes when I create a new issue or open a setting, I got the following errors: The root cause of this is that the request goes to a Jira node … Continue reading Configure Traefik Sticky Session in Kubernetes

Reindex Jira Data Center without downtime on Kubernetes


There are two ways to reindex Jira Data Center without downtime on Kubernetes. My Jira cluster runs a statefulSet in kubernetes. The configuration details: https://gist.github.com/jc1518/e6ec84f01e4fbe2e5517a02ed38b24ca DON'T use the following methods if you have livenessProbe to monitor the /status. As your pod may get killed when it is doing the re-indexing. You should monitor / for … Continue reading Reindex Jira Data Center without downtime on Kubernetes

Run Jira Data Center on Kubernetes Part Two


Continue with the part one, let's do some configurations. As the folder /var/atlassian/application-data/jira/shared-home does not exist in the offical Jira image, we need to create it manually in the container or fork the repository and modify the Dockerfile to create it. You should have one pod called jira-0 running now if you did everything correctly … Continue reading Run Jira Data Center on Kubernetes Part Two

Replace Flannel with Weave Net in Kubernetes


The major reason that I replaced Flannel with Weave Net as the Kubernetes CNI is that Flannel does not support multicast. I did not realize it until my test Confluence DC cluster became dysfunctional. There are two Confluence nodes in the Confluence DC cluster. Each one is a pod, they are working fine when they … Continue reading Replace Flannel with Weave Net in Kubernetes