Bamboo deployment on K8s reinitialized after any helm upgrade operation
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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 K8s gets reinitialized after any helm upgrade operation.
Diagnosis
Obtain the default Bamboo
values.yamlfile from the chart:helm show values atlassian-data-center/bamboo > values.yaml- 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 charts is update)
Cause
Caused by BAM-21542 - Getting issue details... STATUS
Solution
Ensure all keys in the sections labeled UNATTENDED-SETUP are added up-front as part of Bamboo values.yaml.