Add support for Silence CRD

[mcbenjemaa]

What is missing?

Definitely having a way of managing Silences through the K8s API, by adding support for Silence CRD.

A lot of people managing silences with different approaches, but it's always cumbersome.

At Giant Swarm, we manage silences through an operator, we call it silence-operator We would love to move the implementation to prometheus-operator and provide it to the community.

Why do we need it? Dynamically manage Silences with prometheus-operator.

Benefits for us (Giant Swarm): less components, better upstream support Environment

N/A

Anything else we need to know?:

I would like to implement this.

Any suggestions?:

• Do I need to do it in separated PRs?
• What kind of e2e test shall I integrate?

[simonpasquier]

The topic was already discussed in #2398. At the very least we can start a design document to discuss the motivation, use cases, possible pitfalls and implementation options.

[marioferh]

Hi, I noticed this issue hasn’t had any recent activity. If no one is currently working on it, I’d be happy to take it on.

[danielmellado]

Hi Mario, I was already taking a look at this and https://github.com/prometheus-operator/prometheus-operator/issues/6508 but let's collaborate on this ;)

[slashpai]

Thanks folks :)

[mcbenjemaa]

Please take a look at the PR https://github.com/prometheus-operator/prometheus-operator/pull/5485 for the Design document.