#5588·microk8s

Strange behaviour

Author: davgiaCreated Aug 21, 2026Updated Aug 25, 2026

Summary

I have updated to microk8s 1.36.2 and I am experiencing a strange behaviour. Basically after a while k9s is not able to show data, it shows nothing, just: "Synchronizing v1/pods in "all" namespace...". But, kubectl get pods works. I have gitlab-runner deployed in the cluster and it fails to create pod. I have tried kubectl run too and it times out and I cannot see the pod. So a lot of problems and I don't understand.

What Should Happen Instead?

I should not have this problems with a cluster that was working fine with 1.35.x version.

Introspection Report

inspection-report-20260821_133638.tar.gz

EDIT:

I use GitOps ArgoCD to deploy in the cluster, and even ArgoCD has a strange behaviour, basically I cannot sync, I do not see changes. It's seems read-only

EDIT2:

The only way to fix it is to cordon/drain the node, stop and restart microk8s and uncordon. But it's only a temporary solution, the problem presents itself later (I guess like 1 day after).