Rafał Boniecki

This would perfectly complement overall spirit of the project - easy coreboot.

This is surprising. I wouldn't expect that defrag will change my compression settings. Default should be whatever is set in fstab. I was expecting this to be the case.

Happens to me with kube_pod_container_resource_requests and "Terminated" pods (but not yet removed by terminated pod garbage collector). KSM version: kube-state-metrics/kube-state-metrics:v2.4.1 I would expect that kube_pod_container_resource_requests would not return terminated pods...

> mDNS support in kube-vip would alleviate some need of [kubernetes-sigs/external-dns#1604](https://github.com/kubernetes-sigs/external-dns/issues/1604) Only for homelab users.

It would be great to have at least information that pod has limits/requests set on any device that is compatible with device plugin framework (so not only gpus) and how...

I would like to have this as well. Using it for ownership (to attach costs and to integrate with chats for incident response)

It's not mentioned by the OP but alertmanagerconfigs CRD should be supported as well. I want to make use of community made rules and alerts provided by various helm charts...

For me it's definitely the latter. Since promtetheusrule is an existing concept that is commonly used throughout many helm charts (it's basically a standard way to package and deliver prometheus...

It almost works in 3.4.2: For this link: `http://grafana.home.local/explore?orgId=1&left=%7B%22datasource%22:%22Loki%22,%22queries%22:%5B%7B%22expr%22:%22%7Bcontainer%3D%5C%22main%5C%22,pod%3D%5C%22${metadata.name}%5C%22%7D%22,%22refId%22:%22A%22,%22editorMode%22:%22code%22,%22queryType%22:%22range%22%7D%5D,%22range%22:%7B%22from%22:%22now-3h%22,%22to%22:%22now%22%7D%7D` _${metadata.name}_ is correctly resolved to a pod BUT %3D is not resolved to a = so loki gets this query: `{container%3D"main",pod%3D"backfill-worker-go62jrw-962151937"}`...

Disable promtail from loki-stack and use separate and newer promtail chart. Works well.