Arthur Silva Sens

Results 148 comments of Arthur Silva Sens

Yeah, agreed @slashpai I believe I've opened this one too early. Let's discuss the graduation of ScrapeConfig to v1beta1 first :)

For code pointers, we want to replicate what was done in [Prometheus spec](https://github.com/prometheus-operator/prometheus-operator/blob/0d918323945ce87f0094c05c153075c0a6edc8de/pkg/apis/monitoring/v1/prometheus_types.go#L272-L279) and [args generation](https://github.com/prometheus-operator/prometheus-operator/blob/0d918323945ce87f0094c05c153075c0a6edc8de/pkg/prometheus/statefulset.go#L233-L235), but for Alertmanager. In alertmanager, the API changes will happen [here](https://github.com/prometheus-operator/prometheus-operator/blob/0d918323945ce87f0094c05c153075c0a6edc8de/pkg/apis/monitoring/v1/alertmanager_types.go#L62) and args generation...

References: Current docs: https://prometheus-operator.dev/docs/operator/troubleshooting/ Source code: https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/troubleshooting.md --- I feel like we could also mention the metrics used to identify rejected resources

Hey @Aankirz, this is awesome to hear! You can start working on the issue even without the assignment :)

I have a different opinion 😬, getting started usually targets less experienced people with the project, and having the lowest barrier of entry can be a good goal to measure...

Interesting problem! When you used VPA on statefulsets, the Prometheus-Operator did not override the changes made by the VPA?

A quick work around is to remove the scale subresource from the CRD before installing it, the operator should work even without those fields

> No, the way VPA works is that it doesn't change the StatefulSet, it changes the pod when it's being scheduled, and then the pod gets an annotation which tells...

Also, I'm not an expert in contributions to Alertmanager CRDs, but do we need to add this field to the v1beta1 API?

Just curious, what vulnerability exactly can be exploited (and how) if a container doesn't have the `/etc/os-release` file?