monitoring update to 88.3.0-bb.1

Package Merge Request

Package Changes

https://repo1.dso.mil/big-bang/product/packages/monitoring/-/blob/88.3.0-bb.1/CHANGELOG.md

Package MR

big-bang/product/packages/monitoring!500 (merged)

For Issue

Closes big-bang/product/packages/monitoring#383 (closed)

Upgrade Notices

Monitoring now uses cert-manager to issue and inject Prometheus Operator admission-webhook certificates by default. Big Bang now enables its integrated cert-manager package by default; ensure it is deployed and healthy before upgrading monitoring.

If you already deploy cert-manager outside of Big Bang, do not deploy a second cert-manager instance. Set certManager.enabled: false for the Big Bang cert-manager package, keep the external cert-manager deployment enabled and healthy, and ensure its CRDs and controllers are ready before upgrading monitoring. Running two cert-manager installations can cause ownership conflicts over cluster-scoped resources and competing controllers/webhooks. The monitoring package must still have access to the external cert-manager installation to issue the admission-webhook certificate.

Deployments previously using kube-webhook-certgen must either migrate to cert-manager or explicitly retain the supported patch method by setting upstream.prometheusOperator.admissionWebhooks.certManager.enabled: false, upstream.prometheusOperator.admissionWebhooks.patch.enabled: true, and providing an approved patch image. Do not disable both cert-manager modes. The webhook uses Ignore only during initial installation and switches to Fail on upgrades once the webhook should be available. For more details see the monitoring migration doc.