monitoring update to 75.6.1-bb.4

Package Merge Request

Package Changes

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

Package MR

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

For Issue

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

Upgrade Notices

Preview of upcoming bb-common implementation

This release of monitoring incorporates the new bb-common network policy implementation. For most customers, this should require no configuration changes, with one caveat outlined below.

This new functionality allows big bang package maintainers and customers alike to more easily define the network policies that are applied to their packages. This implementation has been added to monitoring as a sort of "trial run." There may be changes to how this implementation works in the future, so consider it in an "alpha" state as far as stability guarantees go. Still, we encourage you to read the docs, become familiar with the pattern, and provide us feedback.

Change to outbound alertmanager connectivity configuration

Previously the monitoring package had a togglable NetworkPolicy that allowed the alertmanager pods to reach out to any destination on the internet for the purposes of integrating with external alerting systems. This is still possible, but the previous configuration option has been removed.

If you were previously setting this value in monitoring:

networkPolicies:
  alertmanager:
    enableEgress: true

You'll now set this more explicit value instead:

networkPolicies:
  egress:
    from:
      alertmanager:
        to:
          cidr:
            # Replace with any CIDR you'd like, but 0.0.0.0/0 allows egress to anywhere.
            # If you need multiple CIDRs, just add another key below this one with the
            # extra CIDR and set it to `true`. Check out the docs linked above for more
            # information.
            0.0.0.0/0: true