CrashLoopBackOff on new installed microk8s v1.25.4 ubuntu 22.04

[marxangels]

ubuntu@r86s:~$ microk8s.kubectl -n kube-system get pod
NAME                                       READY   STATUS             RESTARTS      AGE
calico-node-tfk2s                          1/1     Running            0             5m21s
calico-kube-controllers-64b755c867-kjqz8   0/1     CrashLoopBackOff   4 (71s ago)   5m21s

ubuntu@r86s:~$ microk8s.kubectl -n kube-system logs calico-kube-controllers-64b755c867-kjqz8 
2022-12-25 11:21:41.741 [INFO][1] main.go 98: Loaded configuration from environment config=&config.Config{LogLevel:"info", WorkloadEndpointWorkers:1, ProfileWorkers:1, PolicyWorkers:1, NodeWorkers:1, Kubeconfig:"", DatastoreType:"kubernetes"}
W1225 11:21:41.742004       1 client_config.go:617] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
2022-12-25 11:21:41.742 [INFO][1] main.go 119: Ensuring Calico datastore is initialized
2022-12-25 11:21:51.742 [ERROR][1] client.go 272: Error getting cluster information config ClusterInformation="default" error=Get "https://10.152.183.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": context deadline exceeded
2022-12-25 11:21:51.743 [FATAL][1] main.go 124: Failed to initialize Calico datastore error=Get "https://10.152.183.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": context deadline exceeded

[marxangels]

#3085

[marxangels]

Microk8s v1.26.0 installed successfully to Ubuntu Desktop 22.04.1 LTS

sudo vi /etc/default/grub
# edited
GRUB_CMDLINE_LINUX="cgroup_enable=memory cgroup_memory=1 systemd.unified_cgroup_hierarchy=0"
sudo update-grub

sudo ufw disable
sudo shutdown -r now

# sudo snap remove microk8s --purge
sudo snap install microk8s --classic --channel=latest/stable