ISAF87

I executed the following: ```microk8s enable observability --kube-prom-stack-version=51.8.1``` Output: Infer repository core for addon observability Addon core/observability is already enabled Also tried to disable the addon, and re enable it...

plugging: #3678 would certainly help for scenarios like this.

Thanks for the update. I don't have a fresh cluster, so I took the following steps: 1. Check the current version: ` microk8s kubectl describe -n observability deploy/kube-prom-stack-grafana | grep...

Thank you for the quick response! Did some checks based on your suggestion: 1. `microk8s helm repo list` => Shows prometheus-community helm repo was already present. 2. `microk8s helm repo...

Been digigng a bit in the source of [windows.pod.rules..yaml](https://github.com/prometheus-community/helm-charts/blob/main/charts/kube-prometheus-stack/templates/prometheus/rules-1.14/windows.pod.rules.yaml) It contains these lines: ``` {{- $kubeTargetVersion := default .Capabilities.KubeVersion.GitVersion .Values.kubeTargetVersionOverride }} {{- if and (semverCompare ">=1.14.0-0" $kubeTargetVersion) (semverCompare "

Decided to bite the bullet and run it without the --reuse-values argument Seems to be working, although I did get a couple of warnings Did get a couple of warnings:...

The vulnerability was no longer listed in the security scan so everything seems fine now. Are actions required to ensure the used charts are updated with the microk8s release?

Any update regarding this issue? I am running dapr on a local kubernetes cluster (docker desktop) After deploying 2 api's using aspire.net I get the following: kubectl logs checkout-7cdd565b5-fh7ck -c...

Ran into the same issue after updating to v4.38.0. Before that I never experienced any issues. First I checked WSL service as explained above, which was running. Next I updated...