pfrydids

This is also explained in the closed issue https://github.com/hashicorp/terraform-provider-kubernetes/issues/1625 It is curious though that I can use the alternative https://registry.terraform.io/providers/gavinbunney/kubectl/latest/docs/resources/kubectl_manifest without issue i.e. plan without needing to make a k8s...

@ktsakalozos Side loading requires microk8s to have been installed. Installing microk8s as part of machine image build means that the node name has been chosen (by microk8s). A subsequent launch...

Work around involving two local-execs: ``` resource "null_resource" "migration" { # this local-exec will have its output suppressed provisioner "local-exec" { command =

Any update on this?

There are some closed stale issues that relate to this as well #3080 #3158

> Is it correct that you are looking for a toggle with reduces the scope of the prometheus-operator to the current scope? Same has grafana.rbac.namespaced? That would be a a...

@zaljic when I have set `grafana.rbac.namespaced` to `true` there were no errors but the dashboards that come with `kube-prometheus-stack` do not show up anymore the list is empty.

The following cluster role, role and role binding can be applied on top of the helm deployment of `kube-prometheus-stack` and seems to work (though without `grafana.rbac.namespaced` set to `true`) [kube-prometheus-stack-operator-.zip](https://github.com/prometheus-community/helm-charts/files/14374152/kube-prometheus-stack-operator-.zip)...

> > Any update on this? > > You can test #4283 I have cloned your repo and - in the charts directory run `mv kube-state-metrics prometheus-node-exporter prometheus-windows-exporter grafana kube-prometheus-stack/chart`...

@jkroepke This allows for a clean deployment with the cluster role no longer having cluster wide secrets read permissions BUT when I have set grafana.rbac.namespaced to true there were no...