elasticsearchKibana update to 1.20.0-bb.0

Package Merge Request

Package Changes

https://repo1.dso.mil/big-bang/product/packages/elasticsearch-kibana/-/blob/1.20.0-bb.0/CHANGELOG.md

Package MR

big-bang/product/packages/elasticsearch-kibana!315 (merged)

For Issue

Closes big-bang/product/packages/elasticsearch-kibana#218 (closed) and big-bang/product/packages/elasticsearch-kibana#215 (closed)

Upgrade Notices

Important: If prometheuselasticsearchexporter is enabled (metrics.enabled to true) in the ElasticsearchKibana package, upgrading to 1.20.0bb.0 involves changes to immutable selector labels that requires the elasticsearchmetrics deployment to be deleted before upgrading the release.

The ElasticsearchKibana autoRollingUpgrade field in values.yaml can deploy a preupgrade job that automates the required deployment deletion without any additional steps by using a helm preupgrade hook, so no additional actions is required. It should be noted, a brief outage is expected during upgrade while the elasticsearchmetrics deployment is being rolled out.

However, if you would rather manually delete the elasticsearchmetrics deployment prior to upgrade, then you would need to set the autoRollingUpgrade.enabled=false in the values.yaml and follow steps outlined below. The below command assumes that the ElasticsearchKibana package is deployed in the default Big Bang logging namespace for ElasticsearchKibana, one should look to confirm the namespace of their ElasticsearchKibana deployment:

kubectl delete deploy l app=metrics n logging

Once the resources have been deleted, you can upgrade the release.

added botmr elasticsearchKibana fluentbit statusdoing labels

assigned to @kliu

changed the description

requested review from @chris.oconnell, @michaelmartin, and @andrewshoell

marked this merge request as ready

changed the description

added statusreview teamObservability labels and removed statusdoing label

changed milestone to %2.39.0

Tracking on !5300 (comment 2618278), to create a separate directory and break out chart for upgrade.

added statusdoing label and removed statusreview label

added debug label

marked this merge request as draft

marked this merge request as ready

added statusreview label and removed statusdoing label

added botmr label and removed botmr label

requested review from @troymobley and @cbowmanclare

resolved all threads

Thinking we wait on !5300 (comment 2618278) to queue up too before pulling this one in. Probably worth waiting until 2.40.0. Thoughts @kliu @chris.oconnell @andrewshoell ?

changed milestone to %2.40.0

resolved all threads