Jump to Content
Onify SupportHomeGuidesBlueprintsCommunityChangelogAPI ReferenceGet support
HomeGuidesAPI ReferenceChangelogCommunity
HomeGuidesBlueprintsCommunityChangelogAPI ReferenceGet supportLog InOnify Support
Log In

Community

Ask a Question
ANSWERED

calico pod-controllern does start after updating microk8s

After a auto update of microk8s it seems that we have a issue with the `calico-kube-controllers` pod. It does not start and says `CrashLoopBackOff`. ``` $ microk8s.kubectl get pods -n kube-system calico-node-c7h46 1/1 Running 1 (7m38s ago) 10m calico-kube-controllers-5ddf994775-gp8cv 0/1 CrashLoopBackOff 7 (34s ago) 10m ```
microk8sinfra
Posted by Robert Lundsten 10 months ago
  • FAQs
  • Recent
  • Popular
  • Unanswered
1.26.0actionactionsadfsagentanalyticsansibleapibankidblueprintbootstrapbpmnbulkbulletinbulletinscertcloudconnectorcontainercontent managementcookiecsscustomcustomizationdashboardsdata sourcedeploydockerdocument managementdownloadelasticsearchencodingexportfeature implementedfeature requestfeaturesfilesfirewallflowformsfunctionsgeneralgitgoogleiconsindexinginfraintegrationitemitemsk8sknowledge basekubernetesloginlogsmappingsmemorymicrok8smonitoringngnixopenshiftoperationsospdfportspower bipowershellprintprocessesprometheuspugpythonqlikresourcesrestapirsssamlscriptsearchservicenowshortcutssidebarsortsshsslssotlstooltipstransformtranslationunmanagedupgradeuservideowidgetsworkflowworkflowsworkspaceworkspaceszendesk