You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you for your work, this project is truly amazing, it helps a lot and saves plenty of time!
The kube-hetzner module sets up a default LoadBalancer and ships cert-manager by default even though hetzner does have managed certificates. When deploying a kubernetes service via terraform the LoadBalancer has only a service for http on 80. A service for https for port 443 is missing and I would expect it to be created, such that https://foo.com can be reached via the LoadBalancer IP.
LoadBalancer Services: tcp:80 -> 30127
Aparently changing switching the alorithm_type from from round robin to least connection or vice versa leads to the SSL service being created. However as soon as a new kubernetes service is deployed, the LoadBalancer Service on port 443 is removed again.
I wonder what is responsible for creating/deleting the services. Also Hetzner has managed certificates which can be attached to a LoadBalancer directly, what is the purpose in using cert-manager?
Steps to reproduce:
Use the following kube.tf config
Use the following config including:
ClusterIsser
Deployment (port: 3333)
Service (port: 80, target_port: 3333, type: LoadBalancer)
Description
First of all, thank you for your work, this project is truly amazing, it helps a lot and saves plenty of time!
The kube-hetzner module sets up a default LoadBalancer and ships
cert-manager
by default even though hetzner does have managed certificates. When deploying a kubernetes service via terraform the LoadBalancer has only a service for http on80
. A service for https for port443
is missing and I would expect it to be created, such that https://foo.com can be reached via the LoadBalancer IP.LoadBalancer Services: tcp:80 -> 30127
Aparently changing switching the alorithm_type from from round robin to least connection or vice versa leads to the SSL service being created. However as soon as a new kubernetes service is deployed, the LoadBalancer Service on port 443 is removed again.
I wonder what is responsible for creating/deleting the services. Also Hetzner has managed certificates which can be attached to a LoadBalancer directly, what is the purpose in using
cert-manager
?Steps to reproduce:
kube.tf
configKube.tf file
Logs
Screenshots
No response
Platform
Fedora release 41 (Forty One)
The text was updated successfully, but these errors were encountered: