Closed p1-repo-sync-bot[bot] closed 3 months ago
It turned out there was already egress network policy for alertmanager: https://repo1.dso.mil/bigbang/product/packages/monitoring/-/blob/main/chart/templates/bigbang/networkpolicies/egress-tls.yaml?ref_type=heads I am closing this issue. I tested the alertmanager sending out message to external Slack application with following values set:
monitoring:
enabled: true
values:
istio:
hardened:
enabled: false
networkPolicies:
enabled: true
# -- This toggle enables a NetworkPolicy that will allow external egress providing the ability to send alerts to external resources like MM/Slack/etc.
alertmanager:
enableEgress: true
Issue 'Alertmanager requires egress netpol' closed from GitLab side
In order to configure Alertmanager for notifications such as smtp or slack, an egress netpol is needed. The current design blocks egress from this pod and doesn't seem to have a way to configure it within the chart. This requires deploying a separate egress netpol outside of the chart which is not desirable, especially given the chart supports configurations for external notification configurations.
Below is an example of a netpol I created manually in order to allow Alertmanager to send notifications to Slack. It would be preferably to have this enabled when a receiver is configured for the chart.