mrkwtz

> Can you please help us by identifying the open file handles? This will help us diagnose this issue. I think you can run `lsof` to list open file handles....

Hey @feikesteenbergen , thanks for this :) We're currently looking to get started with a project for which we want to use TimescaleDB 2.0 in a MultiNode setup. I guess...

As someone who wanted to use the AWS config profile option with sigv4 please consider mentioning the `AWS_SDK_LOAD_CONFIG` env variable in the docs. I just spent a day figuring it...

We finally are able to ssh into our nodes. Unfortunately because we're out if inotify user watches / instances (don't know yet) we're not :D It turns out the fs.inotify.max_user_instances...

We found the culprit. The privileged promtail pods (

@vadimgusev-codefresh See here, https://github.com/grafana/helm-charts/commit/bd6e0805e0b14e0d5a39fc9b0dada0ee0042ed90

> Few things: > > * everything grafana-related should be in https://github.com/prometheus-operator/kube-prometheus/blob/main/jsonnet/kube-prometheus/components/grafana.libsonnet > * grafana configuration is optional (as seen in https://github.com/prometheus-operator/kube-prometheus/blob/main/jsonnet/kube-prometheus/components/grafana.libsonnet#L69), so reloader sidecar should be too. > >...

@srobbin sound good to me :+1:

Hey @sarath-ig @jibill We ran into the same problem when we upgraded from 2.8.0 to 2.9.3 and it turned out we had set a token in the GitLab webhook configuration...

Sure, but I would also like to make it configurable. Because I guess the increased defaults won't help every use-case. Argo does this also in its workflow controller https://github.com/argoproj/argo/blob/45c792a59052db20da74713b29bdcd1145fc6748/cmd/workflow-controller/main.go#L67-L68