When trying to scale pods for confluence, it doesn't inherit configurations

[Ahmed Attya]

Hello Guys,

I deployed Confluence on Kubernetes Cluster through helm chart of Atlassian. First, I deployed one replica, and I finished setup from web UI and It is ok.


Now when I change replicas to be 2 from values.yaml file or from kubectl command line and tried to access the new pod, it shows me that the database tables already exist and chose me from restart database configurations or continue and overwrite. in both choices it is not the desired behavior because If I continue and overwrite. it will remove everything I have been done in the first pod.

so why this happens and why doesn't the second pod inherit configurations from the first pod??

[Yevhen]

Most likely you don't have shared home configured and the second Confluence pod thinks it's a fresh installation.

[Ahmed Attya]

How I configure shared-home.
I just set enabled to be true in values.yaml file

should I do anything else?

thanks

[Ahmed Attya]

@Yevhen Hello 

can you check the last reply

[Yevhen]

Shared storage is something you need to take care of in your K8S cluster. Atlassian Helm charts don't configure infrastructure for you. NFS, EFS, Azure files, Google File storage - it all depends on the K8S vendor and cloud you use.