If this isn't a known issue with v1.1.2-rc5, I saved the support bundle before nuking the instance and I'm happy to file a bug.

I’ve checked the support bundle file. It seems similar errors happen not only with your image, but there are also lots of certificate errors in the logs for harvester system components:

logs/cattle-system/rancher-68799df576-6kgtk/rancher.log:2023-04-06T23:22:39.960195043Z 2023/04/06 23:22:39 [ERROR] error syncing 'rancher-stable': handler helm-clusterrepo-download: Get "<https://releases.rancher.com/server-charts/stable/index.yaml>": x509: certificate is not valid for any names, but wanted to match <http://releases.rancher.com|releases.rancher.com>, requeuing
logs/harvester-system/harvester-5b6b4994-qq5jf/apiserver.log:2023-04-06T21:05:28.733608477Z time="2023-04-06T21:05:28Z" level=error msg="failed syncing version metadata: Post \"<https://harvester-upgrade-responder.rancher.io/v1/checkupgrade>\": x509: certificate is not valid for any names, but wanted to match <http://harvester-upgrade-responder.rancher.io|harvester-upgrade-responder.rancher.io>"
logs/longhorn-system/longhorn-manager-qfv6g/longhorn-manager.log:2023-04-06T21:05:38.593416886Z time="2023-04-06T21:05:38Z" level=debug msg="Failed to check for the latest and stable Longhorn versions" controller=longhorn-setting error="Post \"<https://longhorn-upgrade-responder.rancher.io/v1/checkupgrade>\": x509: certificate is not valid for any names, but wanted to match <http://longhorn-upgrade-responder.rancher.io|longhorn-upgrade-responder.rancher.io>" node=boogle

However, I cannot reproduce it in my environment with v1.1.2-rc5. Could you let me know if you managed to reproduce this?