Not entirely sure the tls-san value gets applied

[buggtb]

Bug description

I need to check again on another run, but I set the loadbalancer IP in the k3s node config and it replied with:

Unable to connect to the server: x509: certificate is valid for 10.194.186.59, 10.43.0.1, 127.0.0.1, 192.168.1.50, 192.168.1.51, 192.168.1.52, ::1, not 51.159.11.5

Steps to reproduce

Just run some bad terraform code.

Expected behavior

It should have the cert in the list, instead we've got a bunch of instance specific internal ip's. If for whatever reason the tls san stuff doesn't work, another option would be ssh and curl -vk --resolve 172.31.13.97:6443:127.0.0.1 https://172.31.13.97:6443/ping as thats what I use currently.

Example repository

No response

Anything else?

No response

[mrsimonemms]

When was the last time you rebased from main? I added it as part of #13.

The local.k3s_server_address_public is either the primary node's public IP, or the public IP of the load balancer. I THINK I did it correctly, but I reserve the right to have introduced a bug through incompetence.

Happy to investigate further if you think this is a problem - I'll need access to Scaleway though as Hetzner masks this problem and I don't have the quota on Azure to produce the resources required.