Differences

This shows you the differences between two versions of the page.

--- eolab:crunchy_cloud:issues:jupyterhub-spawn-failed-certifcate-verify-failed [2024/12/18 12:20] – created jan.sonntag
+++ eolab:crunchy_cloud:issues:jupyterhub-spawn-failed-certifcate-verify-failed [2024/12/18 13:46] (current) – azam01
@@ Line 9: / Line 9: @@
 It could be solved by ssh'ing into the VM running Kubernetes (in our case it was our node00).
+To solve the certificate expiration issue we need to first list and see which certificates have expired.
+To list certificates in microk8s:
+<code>sudo microk8s refresh-certs -c</code>
+This command will output a list of certificates and the time left for their expiration.
+The output looks like this:
+<code>
+The CA certificate will expire in 3284 days.
+The server certificate will expire in 364 days.
+The front proxy client certificate will expire in 364 days.
+</code>
+In our case the ''server certificate'' and the ''front proxy certificate'' had expired
+To renew the certificates we run the following commands:
+<code>
+sudo microk8s refresh-certs -e server.crt
+sudo microk8s refresh-certs -e front-proxy-client.crt
+</code>
+With these commands the certificates are updated and the services are automatically restarted.
 Source: https://discuss.kubernetes.io/t/renew-certificate-in-microk8s-cluster/19826