Yevhen Atlassian Team

@Eric Cleek you must turn on clustering in helm values and keep forceCfgUpdate=true. Right now, Confluence is not looking for confluence.cfg.xml in shared-home (which has setupStep=complete).

How does your confluence.cfg.xml in local-home look like? Also, is clustering enabled in your helm values?

@Eric Cleek most like you have lost data in your shared home which contains confluence.cfg.xml. Now when the confluence starts, it thinks it's in a setup mode (as it it's a new installation). Confluence connects to the DB and wants to initialize it but discovers that the db has existing data in it.

I don't think I can share more than what's in official docs: https://confluence.atlassian.com/bamboo/ephemeral-agents-1236444139.html

Ephemeral agents work just fine on EKS (in fact, they are vendor/cloud agnostic and will work on any K8S cluster really)

@Alejandro Carretero Trejo while I can't answer your licensing questions, I can answer your ephemeral agents questions. Ephemeral agents are deployed to a Kubernetes cluster. AWS ECS is not a Kubernetes engine. Perhaps you mean AWS EKS?

@testerUnito you need to configure session affinity aka sticky cookie for your ingress. 

You need to follow https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#self-signed-certificates

You still have jdbc:postgresql://pgatlaciandb-primary.confluence.svc:5432/confluence_db in your values file. Also, I am not sure if NodePort and Killercoda way of exposing services works well with Confluence. I have tried your configuration and Confluence pod passes readiness probe. Can you share output from kubectl get…

root@confluence-0:/var/atlassian/application-data/confluence# root@confluence-0:/var/atlassian/application-data/confluence# psql -h pgatlaciandb-ha -U confluence confluence_db Password for user confluence: psql (16.3 (Ubuntu 16.3-0ubuntu0.24.04.1), server 14.6) SSL connection (protocol: TLSv1.3, cipher:…

I doubt it's a product issue. Just make sure you use the right hostname. By the way, you may need to set https://github.com/atlassian/data-center-helm-charts/blob/main/src/main/charts/confluence/values.yaml#L900 to true otherwise confluence.cfg.xml won't be re-generated.

@PKAR in your test pod you are using a different hostname while Confluence tries to connect to pgatlaciandb-primary.confluence.svc

@Phill Pafford neither product binaries nor Java version have changed. The underlying OS and packages (especially packages) can change. We regularly rebuild and push images to get patched packages from Ubuntu repositories to mitigate CVEs. May I inquire about your use case? How exactly updating Ubuntu version impacted you?…

Request Body is too large suggests that you need to configure your ingress to allow larger uploads.

Oh, on-prem K8S is like that. If you were in AWS I'd say EBS right away. In VMWare... no idea honestly. Whatever block storage is available. I'd probably look at things like https://github.com/openebs/openebs but honestly it's been ages since I last time had to administer an on-prem K8S cluster.

@Jean-François Couture what's the exact problem? Do you use NFS both for shared home AND local home and it impact performace?

But you did specify bucket name and region?

I think you need to configure 2 separate s3-filestore ids - for avatars and attachments, and pre-create AWS S3 buckets for each of those.

Sorry, I missed it completely that you did enabled this feature. It should be supported for this Jira version as far I know, but I am not a Jira SME.

@SvenF you need to enable this dark feature. See the warning block in https://confluence.atlassian.com/adminjiraserver0912/storing-attachments-in-amazon-s3-1346048178.html

@Remie Bolte no, existing pipelines do not update EOL versions. If a version reached EOL, we stop updating this tag.

forceConfigUpdate is the official way.

@fb-standard-anwendungen can you please elaborate on "generates a new server ID and more". If you deploy a clustered Confluence environment, there must be confluence.cfg.xml in shared home which contains some data like server id, license etc. It should be absolutely safe to regenerate confluence.cfg.xml in local home at…

@Mohamed Saad Taha you can define a sidecar container (fluentd or similar) that will tail logs and send them to Splunk.

It should be possible to deploy Bamboo to an OpenShift cluster and use ephemeral agents for builds. There's no dedicated plugin - you just configure Bamboo server to use OpenShift to schedule build pods.

@Bert van Dijk _TMC_nl_ with this property Jira will push logs to localhost:9880 (the default FluentD port). So if you define a FluentD sidecar for Jira pod, Jira will send logs to that FluentD, and FluentD can then send them to whatever backend you define.

@Gaven Ray looks like a non docker related issue. Can you please take a look at https://confluence.atlassian.com/confkb/confluence-dc-won-t-start-after-upgrade-with-error-invocation-of-init-method-failed-nested-exception-is-java-lang-classcastexception-1094487859.html?

@Gaven Ray is this the complete stacktrace? I wonder what's the last "caused by" is.

https://github.com/atlassian/data-center-helm-charts/blob/main/src/main/charts/bitbucket/values.yaml#L223 you need to set this to true which will enable volumeClaimTemplates in Bitbucket sts spec.

Shared home PVC must be RWX, yours is RWO - that's why the second pod can't mount it.