Yevhen Atlassian Team

@Himanshu Sinha can you please provide output from kubectl describe pod rel-test-bitbucket-0 -n bit-bucket? Events in there will shed some light

Hi @Christian Ludwig I'll let folks from DC deployments have their say of course, but I don't think JSM is supported and Jira software Helm chart won't work with JSM image. At least, swapping image will most certainly lead to failures. Installing as a plugin is an option. @Adam Brokes or @Dylan Rathbone will confirm and…

Ah, I missed that the pod is in pending state. Odds are the PVC has never been bound and the pod has unbound PVCs. Let's take a look at events in kubectl describe. I'd also look at kubectl describe pvc too.

@Himanshu Sinha it's really difficult to say what's wrong without logs. Did you enable nfs permission fixer? I expect this init container to fail first if there are permissions issues in the volume. By the way, EFS isn't officially supported as storage backend for Bitbucket due to performance issues. As to NFS, I guess the…

@Medhat Ahmed I guess you'll find https://atlassian.github.io/data-center-helm-charts/ helpful. Yes, Jira is officially supported on EKS, however, you can use the Helm chart to deploy it to most K8s clouds, including on-prem clusters.

Hi @Choo Jaimin Even though OpenShift isn't officially supported, it is possible to deploy Atlassian products to OpenShift. You may need to avoid setting security context and let OpenShift do that (unless you allow anyuid). As to connectivity, you need to make sure images are accessible for your OpenShift cluster. Perhaps,…

@Munjal Patel I have just checked: * a fresh 8.19.0 installation * upgrade to 8.19.1 Both Jira software and core were correctly updated. I wasn't able to reproduce the issue. Do you have a sandbox environment to try the same scenario i.e. a fresh deployment and an upgrade? And as @Dylan Rathbone suggested, sharing your…

@Munjal Patel yes, sorry I did't pay attention that it's a shared home directory. Upgrade of a Helm chart is about pulling and running a new image of Jira Software. Can you please share a screenshot of what you see in UI after the upgrade? What happens in K8s does not differ from Jira upgrade in a VM world - new Jira…

Hi @Munjal Patel I think you may need to take a look at: * https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#additional-libraries-plugins * https://github.com/atlassian/data-center-helm-charts/blob/main/src/main/charts/jira/values.yaml#L568 In other words, your installed plugins need to be…

Hi Tom! Nice essay btw :) Yes, EFS isn't officially supported, and it's not supported in the VM or container world. As far as I know, performance is the key here. When it comes to git, branches and refs, and potentially millions of files, there are risks of big issues with git. Well, I guess you already know that. Here's…

Hm... it is possible that when TLS termination happens on NLB, requests go to Nginx are then passed to Bitbucket without x-forwarder-for or -proto headers. Can't confirm such a use case though. My most recent tests with EKS were with TLS termination on Nginx level not NLB.

@Charlie Misonne yes, if DB settings changed, you'll need to update them in cfg file. Python entrypoint in the image will generate the file, however, it'll skip it if it exists. You should even see some logs saying that. So yes, it looks like moving cfg file to a volume and making edits there is the fastest way to migrate.

Hey Charlie! I guess you do not need an entire home dir. Just some critical directories. Unfortunately, I am not well versed in what are those for Confluence (I am a Bamboo guy :) ) If you have a PVC bound to a PV, I'd probably start a throw away pod with a command like tail -f /dev/null, mount home using this PVC, and…

@Charlie Misonne you will have to migrate home directory that has config file - if it exists it won't be recreated. So, when migrating, I'd start with migrating home directory to a volume (PVC in case of K8s) and run the container with JDBC envs. This should be enough. Btw, have you…

@Reethu How did you create your pipeline yml? Have you checked this doc?

What you can also do is write a little Python or Golang program that would save bamboo-agent.cfg.xml to a configmap, patch a statefulset or deployment and restart. Not ideal, but this way you will save the xml as a configmap and mount it as a file, so that it's persisted across restarts.

Hi Craig! Yes, you are right, this is a networking error and it is caused by the fact that Maven cannot download libraries from Maven central. What happens when you add a specs repo in UI is: * Bamboo tests connection to a remote host, clones the repo * looks for bamboo-specs directory, and pom.xml in particular, to run a…