fix: add tls sans options for k3s too (#1170)

* fix: add tls sans options for k3s too

Signed-off-by: Devin Buhl <devin@buhl.casa>

* chore: update comment

Signed-off-by: Devin Buhl <devin@buhl.casa>

---------

Signed-off-by: Devin Buhl <devin@buhl.casa>

bootstrap/vars/config.sample.yaml

@@ -4,7 +4,6 @@
 #
 
 # Distribution can either be 'k3s' or 'k0s'
-# Note that changing this to k0s will ignore `system_upgrade_controller` in the addons.
 bootstrap_distribution: k3s
 
 # Github username (e.g. onedr0p)
@@ -43,12 +42,12 @@ bootstrap_cloudflare_tunnel_id:
 # CIDR your nodes are on (e.g. 192.168.1.0/24)
 bootstrap_node_cidr:
 # The IP address of the Kube API, choose an available IP in your nodes network that is not being used
-# (Optional) Leave this blank if you are deploying a single master node, this will disable kube-vip in k3s
-# or keepalived in k0s and use the master node IP instead
+# Leave this blank if you are deploying a single master node, this will disable kube-vip in k3s
+# and keepalived in k0s and use the master node IP instead
 bootstrap_kube_api_addr:
-# The hostname of the Kube API, set this if you intend to call the Kube API by hostname rather than IP
-# (Optional) This is currently only utilized in k0s and is added to the Kube API cert sans
-# bootstrap_kube_api_hostname:
+# (Optional) The hostname of the Kube API, set this if you intend to call the Kube API by
+# hostname rather than IP. Hostname is added to the Kube API cert sans
+bootstrap_kube_api_hostname:
 # The Load balancer IP for k8s_gateway, choose an available IP in your nodes network that is not being used
 bootstrap_k8s_gateway_addr:
 # The Load balancer IP for external ingress, choose an available IP in your nodes network that is not being used