Feature idea summary

Cgroups plugin supports only proportional and max Block IO policies. We should support BFQ scheduler as well. Disk stats for the scheduler are in blkio.bfq.io_service_bytes and blkio.bfq.io_serviced files.

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

Is your feature request related to a problem? Please describe.
When deploying the loki-stack chart as a dependent chart, Helm limitations require that it be deployed into the same namespace as my primary application. I am trying to have the loki-stack deployed into a separate namespace from my primary application.

Describe the solution you'd like
I'd like to see an option for namespa

Feature request

It would be nice to integrate query frontend to the https://github.com/thanos-io/thanos/blob/master/scripts/quickstart.sh so that we can easily test the whole stack.

AC:

1. In-memory result cache config should be supported
2. Would be nice to configure Jaeger for query frontend

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

What happened?

After being fine for a couple days, Prometheus mysteriously started crashing with this error:

level=error ts=2020-09-02T15:16:55.096Z caller=query_logger.go:87 component=activeQueryTracker msg="Error opening query log file" file=/prometheus/queries.active err="open /prometheus/queries.active: permission denied"
panic: Unable to create mmap-ed active query log

goro

@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