Bamboo deployment on Kubernetes reinitialized after any helm upgrade operation

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Bamboo deployment on Kubernetes gets reinitialized after any helm upgrade operation.

Diagnosis

  1. Obtain the default Bamboo values.yamlfile from the chart:

    1 helm show values atlassian-data-center/bamboo > values.yaml

  2. Confirm all keys in the section labeled UNATTENDED-SETUP are present in the configuration. (If any key are not added, Bamboo will run the setup stage whenever Helm chartsis update)

Cause

Caused by BAM-21542 - Partial unattended installation doesn't work at k8s environment.

Solution

Ensure all keys in the sections labeled UNATTENDED-SETUP are added up-front as part of Bamboo values.yaml.

Updated on March 12, 2025
Platform
Data Center only
Product
Bamboo Data Center
On this pageSummaryDiagnosisCauseSolution

Still need help?

The Atlassian Community is here for you.
Ask the Community