Simon Pasquier

The same comment applies to https://github.com/redhat-cop/group-sync-operator btw.

Adding the "Prometheus 3.0" milestone since it could make sense for a new major version to drop deprecated APIs?

The change has been merged in the release-3.0 branch.

To be more explicit (since we've discussed offline with @slashpai), my idea was that all debug info should be stored to a temp directory (with each sub-test debug into its...

Can you double check that the secret data doesn't contain `\n` characters? I see no way that the operator would add them.

Yeah, all public manifests from kube-prometheus should use the HTTPS port by now. It would be nice to have an option to adjust the service definition since most users don't...

Can you share the promehteus-operator deployment manifest as well as the AlertManager and ThanosRuler manifests?

In the meantime, you should be able to use https://prometheus-operator.dev/docs/platform/strategic-merge-patch/ to override the default settings.

:wave: this isn't currently possible. I'd say that users should be able to configure the usual TLS settings for the upstream server: CA file, client cert/key file, server name and...

> Any valid reason if the above is not considered? Some know issues / components that such a change will break? Probably no specific reason why it's not available today....