kjuulh/terraform-hcloud-kube-hetzner
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity

made cluster name in hostname the default

Browse Source
This commit is contained in:
Karim Naufal 2022-03-05 04:10:29 +01:00
parent 4394912162
commit b93087d896
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
terraform.tfvars.example
View File

@ -77,8 +77,8 @@ load_balancer_type = "lb11"
# Allows you to specify either stable, latest, or testing (defaults to stable), see https://rancher.com/docs/k3s/latest/en/upgrades/basic/ # Allows you to specify either stable, latest, or testing (defaults to stable), see https://rancher.com/docs/k3s/latest/en/upgrades/basic/
# initial_k3s_channel = "latest" # initial_k3s_channel = "latest"
# Whether to use the cluster name in the node name, i.e. add the prefix k3s-(cluster_name)- to the nodes? The default is "false". # Whether to use the cluster name in the node name, i.e. add the prefix k3s-(cluster_name)- to the nodes? The default is "true".
# use_cluster_name_in_node_name = true # use_cluster_name_in_node_name = false
# Adding extra firewall rules, like opening a port # Adding extra firewall rules, like opening a port
# In this example with allow port TCP 5432 for a Postgres service we will open via a nodeport # In this example with allow port TCP 5432 for a Postgres service we will open via a nodeport

2
variables.tf
View File

@ -123,6 +123,6 @@ variable "extra_firewall_rules" {
variable "use_cluster_name_in_node_name" { variable "use_cluster_name_in_node_name" {
type = bool type = bool
default = false default = true
description = "Whether to use the cluster name in the node name" description = "Whether to use the cluster name in the node name"
} }