Renovate Update Ironbank and auto-upgrade job

General MR

Summary

Renovate update for the following issue and include a auto-upgrade job that deletes the deployment for 1.20.0-bb.0 to automate the manual intervention that was in upstream chart breaking change.

Relevant logs/screenshots

(Include any relevant logs/screenshots)

Linked Issue

#218 (closed) #215 (closed)

Upgrade Notices

Important: If prometheus-elasticsearch-exporter is enabled (metrics.enabled to true) in the Elasticsearch-Kibana package, upgrading to 1.20.0-bb.0 involves changes to immutable selector labels that requires the elasticsearch-metrics deployment to be deleted before upgrading the release.

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

However, if you would rather manually delete the elasticsearch-metrics 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 Elasticsearch-Kibana package is deployed in the default Big Bang logging namespace for Elasticsearch-Kibana, one should look to confirm the namespace of their Elasticsearch-Kibana deployment:

kubectl delete deploy -l app=metrics -n logging

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