Community

When trying to connect Kubernetes cluster I get this error: Unable to connect to the server: x509: certificate has expired or is not yet valid: current time 2024-04-02T11:50:40Z is after 2024-03-26T10:30:10Z. It seems that some cert has expired. What do I need to do?

microk8s

2 years ago by Robert Lundsten

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.

microk8sinfra

4 years ago by Robert Lundsten

1.26.0 action actions adfs agent aks analytics ansible api azure backup bankid blueprint bootstrap boundry bpmn bug bulk bulletin bulletins camunda cert cloud connector container content management cookie css custom customization dashboards data source debug deploy docker document management download elasticsearch encoding export feature implemented feature request features files firewall flow forms functions general git google helix icons indexing infra integration item items javascript k8s knowledge base kubernetes logging login logs maintenance mappings memory microk8s monitoring ngnix notifications npm openshift operations os pdf ports power bi powershell print process processes prometheus pug purge python qlik query refresh regexp resources restapi routes rss saml script search servicenow settings shortcuts sidebar sort ssh ssl sso theme tls tooltips transform translation unmanaged upgrade user video widgets worker workflow workflows workspace workspaces zendesk

Microk8s: Unable to connect to the server: x509: certificate has expired or is not yet valid

calico pod-controllern does start after updating microk8s