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

Describe the bug
The PodSecurityPolicy included in the Promtail Helm chart does not grant the capabilities needed for running the privileged initContainer when the setting is enabled.

To Reproduce
Steps to reproduce the behavior:

1. Have a cluster with a baseline PodSecurityPolicy which prevents privileged pods.
2. Install promtail chart with initContainer enabled and PSP enabled. T

There is an example in-memory cache config for query frontend in the document https://github.com/thanos-io/thanos/blob/master/docs/components/query-frontend.md#in-memory. However, it is not very clear how to configure these values, what is the correct format, etc.

AC, we should document 4 items:

1. The format of max_size. Based on the flag in Cortex https://github.com/cortexproject/cortex/

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