terraform-hcloud-kube-hetzner/output.tf
Marco Nenciarini 0c3aa36c03
First control plane node is not special anymore
The first control plane node is now identical to any other server
node. The cluster initialization happens once in two steps: first,
make sure that the k3s cluster is initialized and then apply our
configurations while the other nodes join. This change makes the
initialization more resilient and even faster than before.
2022-02-22 13:36:25 +01:00

27 lines
781 B
HCL

output "controlplanes_public_ip" {
value = module.control_planes.*.ipv4_address
description = "The public IP addresses of the controlplane server."
}
output "agents_public_ip" {
value = module.agents.*.ipv4_address
description = "The public IP addresses of the agent server."
}
output "load_balancer_public_ip" {
description = "The public IPv4 address of the Hetzner load balancer"
value = data.hcloud_load_balancer.traefik.ipv4
}
output "kubeconfig_file" {
value = local.kubeconfig_external
description = "Kubeconfig file content with external IP address"
sensitive = true
}
output "kubeconfig" {
description = "Structured kubeconfig data to supply to other providers"
value = local.kubeconfig_data
sensitive = true
}