How to change datasource connection running on kubernetes

fb-standard-anwendungen June 18, 2024

Hello :-)

If I adjust the database URL in values.yaml and sync it to Kubernets, the configuration (database URL) in confluence.cfg.xml does not change. Now there is the parameter "forceConfigUpdate" in values.yaml. This corrects the database URL, but unfortunately also generates a new server ID and more. So for me this parameter "forceConfigUpdate" cannot be used to adjust the database URL. I then manually adjusted the database URL in the confluence.cfg.xml file, which works, but what is the official way from Atlassian for Confluence? I only found these two links, but they are not applicable for our Kubernets environment (https://confluence.atlassian.com/doc/configuring-a-datasource-connection-937166084.html and https://confluence.atlassian.com/confkb/how-to-generate-a-new-confluence-cfg-xml-425461512.html). Thank you very much for your feedback

1 answer

0 votes
Yevhen
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 18, 2024

@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 any time.

fb-standard-anwendungen June 18, 2024

I am currently still in the test phase and therefore Confluence is running as a single node configuration. Don't worry, the confluence.cfg.xml file is persistent. This is also generated/configured once (during the initial setup) with the correct values from the values.yaml. However, if I now want to change the database URL, I assumed that I would only have to change this in values.yaml (which would actually be the case according to Kubernetes). But after syncing the new values.yaml, the changes are NOT applied, even after a pod restart. I can of course delete the statefulset (but you shouldn't do that :-)) or set the parameter forceConfigUpdate to true (but you shouldn't do that in a running environment either because a new server ID will then be generated and more!) But how do you do it then? I need an official way from the manufacturer to make sure ;-).

Yevhen
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 19, 2024

forceConfigUpdate is the official way.

fb-standard-anwendungen June 19, 2024

thanks for the answer

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.5.5
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events