Simon Pasquier

> If that parameter is omitted, does that cause AlertManager to then listen on all addresses / interfaces? If so, that seems like a viable solutuon. By default, Alertmanager will...

superseded by #2752

I'm changing the issue type from `feature` to `documentation` since it's possible to use `ScrapeConfig` for this use case. The new goal would be to write documentation based on https://github.com/prometheus-operator/prometheus-operator/issues/3931#issuecomment-2668013334

TestMarshallServiceMonitor() breaks but I feel that we can remove it (there's no direct value in testing the output of the JSON standard library).

The root issue is https://github.com/prometheus/sigv4/issues/14. Once it is fixed, it should trickle down here.

Thanks for the PR! I imagine that you'll prepare a similar PR for github.com/prometheus/prometheus. Since the operator pulls the sigv4 dependency from it, it might be more convenient to wait...

Just to be sure to understand, what you're looking for is the following: * The operator doesn't enforce the namespace value in the routing for all AlertmanagerConfig resources located in...

Ok I've looked at the PR in more details and I can see the benefit. I forgot that the AlertmanagerConfig objects in the Alertmanager would have `continue: true` so there's...

Another option would be to define something akin to `.spec.excludedFromEnforcement` for Prometheus which allows to exclude some resources from label enforcement. I think that I prefer your approach because *...

I've edited the issue's title to make it more obvious that it's about network policies for the Prometheus pods. I'd agree that it would be a useful addition and I'd...