The PR is #4008

Last time I tried to get this working, the issue was with getting python.d
to properly load the Yoctopuce modules. As far as I could tell at the time, the dynamic import thing works, it's just an issue with getting Python to properly import modules that aren't in system.path, but I didn't look very deep beyond that. Part of the problem there is that the Yoctopuce Python

Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

Hello Loki team,

First and foremost, thank you so much for Loki! It's awesome.

Is your feature request related to a problem? Please describe.
As a cluster administrator, when installing loki-stack
I want to be able to set toleration for promtail
So that I may forward logs from all nodes, even nodes with taint, to loki

Describe the solution you'd like
I would like to be able to

It works in API level: https://thanos.io/tip/components/query/#store-filtering would be nice to have some UI support for it (:

This is a reminder for me or a task if anyone wants :P

Basically, The last two questions aren't really regex's questions.

To do:

• Move said questions to correct place.
• Add new regex questions (Python related!)?
• Maybe add a new ## Regex section, as it is a valuable skill

@bwplotka introduced a new streaming remote read in Prometheus, we should add the same to Cortex for people who point Prometheus and Thanos at Cortex.

This is a FEATURE REQUEST.

Please add support for kube_state_metrics_build_info as part of the metrics exposed on telemetry port 8081.
kube_state_metrics_build_info shall include the version of the kube-state-metrics.
Most Prometheus exporters are currently supporting such metric.

What did you expect to see?

I'm expecting to be able to filter out the requests from blackbox exporter in my access logs.
So, please, add a user agent header that container the "blackbox exporter" string somewhere.

What did you see instead?

I see User-Agent: Go-http-client/1.1
Not easy to filter in the access logs...

It would be awesome if the metrics could include the node's topology.kubernetes.io/region & topology.kubernetes.io/zone (not sure what the non-AWS fields are called). That would help quickly identify patterns in the results. e.g., zone "a" is slower than zone "b" or that cross-zone traffic is what's causing a large spike in response times. Not sure if this is possible within the framework of this