Arthur Silva Sens

Hi rgoltz! I don't mean to sound rude, but this sounds like a limitation of the vulnerability scanner... it doesn't sound like something we should be solving on our side....

Hey 👋 Could you share a CPU profile with us? That way we can understand where the prometheus-operator is using its CPU cycles. Maybe also some extra info, like cluster...

What impresses me is that 50% of CPU time is spent on GC. It should be around 20%, isn't it?

> @simonpasquier is there already existing code for the other crds checking the singularity? Then I'd reuse it... Since k8s doesn't allow the same resource kind, with the same name...

Looks like the rebase was done incorrectly 😅, we don't want to merge 37 unrelated commits

Hey @janluak , have you noticed the commits that were added by accident here? Do you need some help with the rebase?

What I usually do is use the git rebase command in interactive mode: `git rebase -i HEAD~` I believe in the case of this PR you'd work with 37 commits...

Hey @janluak, thanks for your interest in helping out. To add new fields to scrapeConfig CRD: You'll want to add new fields to the Spec [here](https://github.com/prometheus-operator/prometheus-operator/blob/0d918323945ce87f0094c05c153075c0a6edc8de/pkg/apis/monitoring/v1alpha1/scrapeconfig_types.go#L98C11-L98C11). The config is generated...

Could we change de fsGroup depending on the thanos version used?

Hey, thanks for the interest and initiative to open a pull request about the issue is there any reason not to use the already existing flag --listen-address to manage the...