Waiting for load-balancer to get an IP... #922
-
DescriptionHello. We planned to use this module for production and development environments, but during the dev phase, there was a problem with module.kube-hetzner.null_resource.kustomization. Everything worked fine until today. Please help us fix this. Can we do this without rebuilding the cluster? I also have a question. Can we add other servers to the network that creates a module for itself, for example, a separate instance for Jenkins outside of the cluster? Will this not break the module?
Kube.tf filemodule "kube-hetzner" {
providers = {
hcloud = hcloud
}
hcloud_token = var.hcloud_token
source = "kube-hetzner/kube-hetzner/hcloud"
ssh_public_key = var.pub
ssh_private_key = var.priv
network_region = "eu-central"
create_kubeconfig = false
create_kustomization = false
use_control_plane_lb = true
lb_hostname = "hostname"
control_plane_lb_type = "lb11"
enable_rancher = true
initial_k3s_channel = "v1.25"
rancher_hostname = "hostname"
cluster_name = "k3s"
automatically_upgrade_k3s = false
automatically_upgrade_os = false
ingress_controller = "nginx"
control_plane_nodepools = [
{
name = "control-plane",
server_type = "cx31",
location = "fsn1",
labels = ["role=master"],
taints = [],
count = 3
# Enable automatic backups via Hetzner (default: false)
# backups = true
},
]
agent_nodepools = [
{
name = "agent-development",
server_type = "cpx41",
location = "fsn1",
labels = ["environment=development", "role=worker"],
taints = [],
count = 2
# Enable automatic backups via Hetzner (default: false)
# backups = true
},
{
name = "agent-jenkins-main",
server_type = "cx41",
location = "fsn1",
labels = ["environment=jenkins"],
taints = [],
count = 0
# Enable automatic backups via Hetzner (default: false)
# backups = true
},
{
name = "agent-redis-dev",
server_type = "cx21",
location = "fsn1",
labels = ["environment=redis"],
taints = [],
count = 1
# Enable automatic backups via Hetzner (default: false)
# backups = true
},
]
load_balancer_type = "lb11"
load_balancer_location = "fsn1"
} ScreenshotsNo response PlatformLinux |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 11 replies
-
Same issue for me |
Beta Was this translation helpful? Give feedback.
-
@grig0701 @Keyruu Sometimes the Hetzner systems are slow, you retry. And if it does not work, upgrade to the latest version, see readme. I just tested it works now. @grig0701 Regarding your second question, of you could can deploy other instances, terraform makes this easy, as you can include our module in a greater terraform project. |
Beta Was this translation helpful? Give feedback.
-
I just had a quick look. When using nginx as the Ingress Controller, it states to use a Domain name for the main Load-Balancer, which results the service not to get assigned an IP address but the selected domain name. |
Beta Was this translation helpful? Give feedback.
-
@MoergJ @M4t7e Currently reverting #908 completely. And we will improve the logic from there in the future. |
Beta Was this translation helpful? Give feedback.
-
@M4t7e Perfect, thanks for that, merged and preparing a quick release now! |
Beta Was this translation helpful? Give feedback.
-
@mnbro FYI, we had to revert #908 completely as it was causing problems. Whatever problem you had with it hanging in your case, please do open an issue with your kube.tf for us to reproduce and debug it further. |
Beta Was this translation helpful? Give feedback.
-
Yes, it works! Thank you very much for your quick response and correction. Thank you for this beautiful module) |
Beta Was this translation helpful? Give feedback.
-
@MoergJ thanks for the help) |
Beta Was this translation helpful? Give feedback.
@grig0701 @MoergJ @Keyruu FYI, @M4t7e's fix has just been released in v2.5.2. Please test and let us know. Follow the readme well and if you have another issue, please open an issue and share your kube.tf.