Paweł Krupa

As for `{{ grafana_dashboards_dir }}` you are right, this is a bug. We are importing dashboards through an API since it wasn't previously possible to copy dashboards from grafana.net/dashboards directly...

Please do so :)

@SuperQ what about adding hosts/config in a similar way as it is done in blackbox-exporter? This way [the existing Prober mechanism from prometheus-operator](https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/api.md#probe) could be re-used to include smokeping_prober as...

Cannot be easily fixed until kubernetes api server migrates to v1 in https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/authentication/authenticatorfactory/delegating.go#L36

Yes, that's exactly what needs to be done and I started doing that. However, there is a transient dependency on v1beta1 coming from https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/authentication/authenticatorfactory/delegating.go#L36

Asked. This change is not planned yet.

The alternative fix is to use `kubectl apply --server-side` instead of plain `kubectl apply`. This wouldn't add kubectl specific annotation which is the main source of issue here.

> A possible workaround would be to truncate the descriptions with crd:maxDescLen=0, like in crossplane/crossplane#702. Crossplane workaround predates server-side apply functionality being GA in kubectl, by using it we would...

Answered in slack: https://kubernetes.slack.com/archives/CFFDS2Z7F/p1646219889287799

kube-prometheus is deploying node-exporter with [kube-rbac-proxy sidecar](https://github.com/prometheus-operator/kube-prometheus/blob/main/manifests/node-exporter-daemonset.yaml#L55-L81). Sidecar is responsible for RBAC and TLS termination. We are using this architecture for historical reasons as node_exporter did have TLS termination capabilities...