Berkay Tekin Öz

Hey @Aaron-Ritter, Thank you for bringing up good points. I might've been a bit vague in the general process for updates, apologies for that. As I've mentioned before indeed we...

Hey @ACodingfreak, You can utilize the `rook-ceph` addon to connect to an external ceph cluster, or connect to microceph see [the docs page](https://microk8s.io/docs/how-to-ceph) for more information. Thanks.

Hey @ACodingfreak, You can pass the `--storageclass` option when enabling the addon to [set which storage class](https://github.com/canonical/microk8s-core-addons/blob/dd1c33f03117d6dfbebd196e3a14dc2c6578eb39/addons/registry/enable#L20) should be used.

Hey @HeIp, `snap refresh` command without any specific channel specified would try to refresh to the latest revision in the channel the snap is currently tracking, which means you'd only...

Hey @jpbeniopa, Microk8s already supports joining nodes as workers via the `--worker` flag of the join command. This resets the joining node, disables the datastore and any control-plane related services....

Hey @gautamgadipudi-hpe, Thank you for reporting this issue. Is there a script used for joining/creating the cluster? I believe the issue might be related to dqlite not having enough time...

Hey @bigatl22, Have you followed https://microk8s.io/docs/install-raspberry-pi ? I see ``` Jun 10 17:06:57 pi-cluster-m0 microk8s.daemon-containerd[501]: time="2025-06-10T17:06:57.794688830+01:00" level=error msg="RunPodSandbox for &PodSandboxMetadata{Name:calico-node-9q27t,Uid:e045225d-1bb6-4aa8-bb15-6b7e4654141d,Namespace:kube-system,Attempt:0,} failed, error" error="failed to create containerd task: failed to create...

Hey @FATIHISILGAN, Can you share an inspection report for your node? On a first look it seems like the kube-apiserver is struggling / not healthy. We need more logs to...

Hey @Srokap, Thanks for reporting this issue. As far as I'm aware Microk8s and kubernetes has switched to v3 a while back and `--enable-v2` flag was kept around for compatibility...

Hey folks, Here's a workaround guide for getting rid of v2 data and upgrading to 1.34 https://gist.github.com/berkayoz/1a04ebcd95494c08f2f01836cb16dbf9 @Srokap thanks for trying the suggestion out. I've not encountered the issue you...