Maxime Brunet

I have written a couple rudimentary Jsonnet functions that provide an experience similar to `PodMonitor`/`ServiceMonitor` from the `prometheus-operator` ([promcfg.go](https://github.com/prometheus-operator/prometheus-operator/blob/main/pkg/prometheus/promcfg.go)), but not sure if this is something you would want to...

I have shared the utilities here for now: https://github.com/maxbrunet/parca-jsonnet-libs Basically, `s/(Pod|Service)Monitors/\1Profilers/`. Here is the interesting usage bit: [maxbrunet/parca-jsonnet-libs@`743f821`/examples/parca.libsonnet#L10-L69](https://github.com/maxbrunet/parca-jsonnet-libs/blob/743f82116483b01c16f9bcc9db3d7ddc07c6f1d7/examples/parca.libsonnet#L10-L69) Their implementation: * [maxbrunet/parca-jsonnet-libs@`main`/scrape-configs/podprofilers.libsonnet](https://github.com/maxbrunet/parca-jsonnet-libs/blob/main/scrape-configs/podprofilers.libsonnet) * [maxbrunet/parca-jsonnet-libs@`main`/scrape-configs/serviceprofilers.libsonnet](https://github.com/maxbrunet/parca-jsonnet-libs/blob/main/scrape-configs/serviceprofilers.libsonnet) Let me know if there is...

Yeah, I hear you, I am not sure if I want to do that either, but for fun, let me see if I can make a dynamic version list :grin:...

Sweet, it's dynamic :slightly_smiling_face:

Some work has been done in parca-dev/docs#140, going to close in favor of parca-dev/docs#137

@OopsYao's solution works, "Include administrators" needs to be left unchecked in the branch protection rule: > Deploy keys with write access can perform the same actions as an organization member...

> I would also like to know the use-case of surfacing parameters like secureListenAddress or upstream. I do not have a use-case at the moment, my idea is to keep...

> This is conflicting with #1477 for reasons mentioned in [#1500 (comment)](https://github.com/prometheus-operator/kube-prometheus/issues/1500#issuecomment-968700863). Are referring to this specific sentence? Meaning you have not yet decided on a location to ease configuration...

I am at the same point as you on all that. Reading the KEP further, PodAntiAffinity seem to cause them issues and they are even thinking about deprecating it in...

I got the Karpenter documentation clarified aws/karpenter#948 So in short, pod anti-affinities are a strain for the Kubernetes Scheduler at the moment They does not seem to be a clear...