Yevhen Atlassian Team

Wring password sounds like you don't have sticky cookies configured for your ingress (or loadbalancer, depending on how you exposed Bitbucket service). As to node joining issue, it's weird you have it in a 1 node cluster. Can you please share the entire log?

https://hub.docker.com/r/atlassian/jira-software will be supported

@robert.haskins it depends on the files. I suggest you take a look at additionalFiles and additionalConfigMaps in values.yaml. With additionalFiles, you can either create configmaps/secrets outside Helm and have them mounted into containers, or you can define additionalConfigMaps with keys and content, and helm chart will…

@robert.haskins you must have set replicaCount to 2? Setting clustering to false has no impact on the number of pods, it rather sets a few environment variables for the confluence to enable Hazelcast node discovery.

hi @Bryan Guffey there's no difference, well, almost no difference. While additionalFiles imply that you create a configmap outside helm chart, customServerXml belongs to the helm chart and configmap will be created for you (and you keep your server.xml in helm values). You can also use additionalConfigMaps which will also…

Yes, Jira pod won't be marked ready when it's recovering cache, so /status will report 503 or sometimes even 500

Unfortunately, there are no estimates. It also depends on available resources. What Confluence does is uncompresses index snapshots, so it's cpu and io intensive operation. In my most recent tests, 26Gi of indexes were recovered in 5 to 6 minutes (gp2 storageclass)

My bad, it's ATL_FORCE_CFG_UPDATE. See: https://hub.docker.com/r/atlassian/confluence confluence.cfg.xml in local home is generated only if the file does not exist https://bitbucket.org/atlassian-docker/docker-atlassian-confluence-server/src/cda8d93331e361c5d88ea7c1b369f6e0e1f39946/entrypoint.py#lines-18. This behavior can…

@KUNG MIN PARK while the none is recovering index from shared home, it is responding 503 to /status calls from a readiness probe. Until readiness probe passes, the pod isn't marked as ready, and thus no endpoint is created. In other words, traffic does not go from service to such a pod.

Hi @KUNG MIN PARK when you migrated an existing installation, did you enable clustering right away? If you didn't, next time you set clustering.enabled=true, you also need to pass env var UPDATE_CFG=true, because by default if confluence.cfg.xml exists in local-home, image entrypoint won't update it.

@Maddhin you don't need any context path unless you want Confluence to be available at https://your.domain.com/confluence rather than just https://your.domain.com

Hi @Maddhin I suggest that you get rid of those rewrite target and regex annotations in the ingress and set confluence context path: https://github.com/atlassian/data-center-helm-charts/blob/main/src/main/charts/confluence/values.yaml#L522 This way when you hit /confluence on your ingress you will get to /confluence in the…

Hi @Dina ElMowafy While there's no migration guide you can still find the following page helpful: https://atlassian.github.io/data-center-helm-charts/userguide/MIGRATION/ As to the hardware requirements, I'd suggest you try to duplicate what you already have for your DC Jira now, i.e. your memory and cpu requests/limits…

@Tibor Kadar have you tried kubernetes svc directly? https://kubernetes.svc.cluster.local? This will work though only if the runner is in the same cluster.

@Kadriye Taylan yes, Kube is supported. See: https://atlassian.github.io/data-center-helm-charts/ As to storage, all datacenter products need a shared volume - RWX, and a RWO for local home. Not sure if anyone in the community had experience deploying to bare metal k8s. In AWS world, EFS and EBS would be the right storage…

Looks like expected behavior to me. See: https://confluence.atlassian.com/bamboo/agent-authentication-289277196.html

Hi @Phill Pafford when you say it's not working, do you mean security token never makes it to the server? What behavior do you see when the remote agent starts? Anything helpful in logs? Also, do you see the agent in remote agents page on Bamboo server side? If so, which status is it?

Helm charts use LTS tags only and 8.x are not yet LTS. And yes, it is safe to use any image tag with the Helm chart.

@rwm rwm you can easily override the tag when running helm install/deploy, for example ``` helm install bitbucket -n bitbucket --set image.tag=7.21.10 ``` You may also override the tag in your custom values.yaml

@Jorn Van Coillie can you please share you runner pod yaml? Definitely networking messed up.

https://bitbucket.org/atlassian/kubectl-run/src/master/ It's base64 encoded kubeconfig file which you can download from DO.

@王九日 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. 

In one of the solutions I found it was a missing trailing slash in the URL. Can you give it a try with it? It can be context path + some ingress weirdness.

Found https://community.atlassian.com/t5/Confluence-questions/Why-is-my-Confluence-Configuration-stalled-before-entering-a/qaq-p/1653695 and https://community.atlassian.com/t5/Confluence-questions/Can-not-init-confluence-7-3-on-kubernete/qaq-p/1299592 Can you please share your values.yaml? In particular, ingress settings.…

@Ross Brook do you see any errors in browser dev console? Also, can you can logs from /opt/atlassian/confluences/logs?

Hi @Vasanthakumar Velusamy You may want to start with https://atlassian.github.io/data-center-helm-charts/platforms/OPENSHIFT/ A couple of tweaks will be required here and there. It'll be easier if you can enable anyuid for the confluence service account.

@Gaurav Patange you will need at least basic Helm and K8s knowledge to do that. You can get yaml files by running `helm template` against the target Helm chart.

That's the only supported way to deploy DC apps to Kube. If you can't use Helm at all, perhaps, you can do `helm template` save yaml, and then apply it.

Helm charts can be installed on any K8s clusters. You just need to make sure you have storage and networking configured.

@Gaurav Patange you may want to give https://github.com/atlassian/data-center-helm-charts a go.