Shaun

Hi Folks! Facing the same issue: CA Version: v1.21.1 aws-ebs-csi-driver Version v1.10.0-eksbuild.1 Cluster-autosacler logs: ```ruby I0920 17:30:00.585954 1 scheduler_binder.go:803] Could not get a CSINode object for the node "ip-10-121-173-251.ap-south-1.compute.internal": csinode.storage.k8s.io...

We don't have the mentioned tags mentioned above, and it was working earlier. Though, we found the issue was with the scheduler. we are using a custom scheduler.. Our vendor...

Also, from your comment, what do you mean by `When your ASG is at 0`? You mean if I set the desired count to be '0'?

We are using file system as EBS volume and mounting it as pvc

Filesystem on EBS Volume: ext4 Volume Type: gp2 Not using any additional datastore options for k3s. You mean should we try upgrading to v1.24.3+k3s1 and test if this is happening?

vCluster Loft: https://loft.sh/docs/getting-started/explore/virtual-clusters We are using vcluster template and we use the k3s image in it. Do you want the yaml output of that? @brandond

Please find file attached. [vcluster-pod.txt](https://github.com/k3s-io/k3s/files/9446217/vcluster-pod.txt)

`❯ k get pvc data-onboarding-test15-0 -o yaml` ```yaml apiVersion: v1 kind: PersistentVolumeClaim metadata: annotations: pv.kubernetes.io/bind-completed: "yes" pv.kubernetes.io/bound-by-controller: "yes" volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/aws-ebs volume.kubernetes.io/selected-node: finalizers: - kubernetes.io/pvc-protection labels: app: vcluster release: onboarding-test15 name:...

Is there a fix yet? Postgres RDS version :14.7 Konga version: 0.14.9

My Grafana version is 8.5.15 and had got the same error. As said in the logs here: ```Ruby lvl=eror msg="Critical error" reason="Grafana has already been migrated to Unified Alerting.\nAny alert...