microk8s v1.24 - refresh-certs doesn't seem to refresh certs

Summary

i have microk8s 1.24 and i need to grant access to the cluster via FQDN … I edited csr.conf.template and i refreshed the certificates as follow

sudo microk8s refresh-certs --cert server.crt sudo microk8s refresh-certs --cert front-proxy-client.crt

i didn’t refresh the ca.ctr because apparently i would have to rebuild the cluster " Warning: refreshing the root CA requires nodes to leave and re-join the cluster" unfortunately it’s not yet working… when i connect to the API server via the FQDN i get connection rejected

Unable to connect to the server: x509: certificate is valid for kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster, kubernetes.default.svc.cluster.local, not [xxxxx.com](http://xxxxx.com/)

i was only able to make it work, after @neoaggelos suggested as workaround, to run sudo snap set microk8s dummy="$(date)"

What Should Happen Instead?

refresh certs should work

Reproduction Steps

add a DNS entry to csr.conf.template and refresh certs

Introspection Report

inspection-report-20220612_111958.tar.gz

Can you suggest a fix?

Are you interested in contributing with a fix?

[HazyFish]

Same on v1.25

[anubisg1]

@neoaggelos is there a reasonable workaround for this? Without this it’s not possible to have the microk8s control plane behind a load balancer.

The workaround is sudo snap set microk8s dummy="$(date)" as described in my initial report