Hetzner, AppDeployment, LoadBalancer - Help needed #11295
-
|
Hi, Step 1 Step 2 Step 3 kubectl get nodes
NAME STATUS ROLES AGE VERSION
usercluster-7c4f4dcdc9-hmk7k Ready <none> 42m v1.24.6
usercluster-7c4f4dcdc9-pf8sr Ready <none> 42m v1.24.6Step 4
kubectl get deployments
hello-world 3/3 3 3 36mStep 5 kubectl expose deployment hello-world --type=LoadBalancer --name=my-serviceand check services But EXTERNAL-IP is still "pending". We annotate service But nothing happen. We wonder why. Everything works on the main cluster where KKP is installed. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 9 replies
-
|
Hi @clickersmudge, the Hetzner CCM (Cloud Controller Manager) and CSI components are automatically installed onto user clusters. You should be able to see Pods with a edit: Setting up a network either in the cluster spec or on the datacenter is required for CCM and CSI to be set up. To identify issues with your load balancer, I'd recommend to review (and perhaps share) I'd recommend to create the Service directly via the proper annotations in a YAML file (for an example, see the Hetzner CCM documentation) instead of using |
Beta Was this translation helpful? Give feedback.
-
|
Following up on this answer here as well for visibility, the Hetzner CCM/CSI installation requires a network to be configured either while going through the cluster wizard or in the datacenter specification in your |
Beta Was this translation helpful? Give feedback.
-
|
Hey @clickersmudge, I've updated this answer to include the information about the network. Is there any other problem you have with Hetzner as a cloud provider in relation to CCM and CSI, or can we mark this answer as the solution to your problem? |
Beta Was this translation helpful? Give feedback.
-
|
@embik Hi, Master/Seed where KKP is installed. User cluster I dont see "hcloud-csi-" on user cluster. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
@embik If you want, we can send you the access data for the development version somewhere on priv. We checked such a scenario: LoadBalancer has been created. It did not have the correct target, but you can see that communication has taken place. KKP Cluster |
Beta Was this translation helpful? Give feedback.
-
|
@clickersmudge I did some digging into the code base to figure this out, is it possible that you haven't set a network name for Hetzner neither while going through the cluster creation wizard nor in the datacenter definition in your |
Beta Was this translation helpful? Give feedback.
-
|
@embik At the start, I would like to thank you very much. We debugged it all weekend. We didn't know if we needed to install a plugin. Is something with the server or maybe we need to install the controller manually. I did some digging into the code base to figure this out, is it possible that you haven't set a network name for Hetzner neither while going through the cluster creation wizard nor in the datacenter definition in your Seed resource? We did not provide this value. When we created the seed, we thought it was optional. We added it, and it actually works. Again thank you very much. |
Beta Was this translation helpful? Give feedback.
-
It's somewhat optional (as you saw, clusters got deployed without it), but it will result in reduced functionality. But this isn't clearly documented, so we need to improve on that. The snippet you shared only alludes to this by saying While machines can be in multiple networks, a single one must be chosen for the HCloud CCM to work.
No, this is the network that will be used for your user clusters. As such, you can use a dedicated network for that (and maybe even should, to separate the KKP installation from any user clusters). |
Beta Was this translation helpful? Give feedback.
Hi @clickersmudge, the Hetzner CCM (Cloud Controller Manager) and CSI components are automatically installed onto user clusters. You should be able to see Pods with a
hcloud-csi-prefix in your user cluster'skube-systemnamespace. In addition, the Hetzner CCM for your user cluster is installed in the seed cluster's namespace for your cluster.edit: Setting up a network either in the cluster spec or on the datacenter is required for CCM and CSI to be set up.
To identify issues with your load balancer, I'd recommend to review (and perhaps share)
kubectl describe svc my-servicethe logs forhcloud-cloud-controller-managerPods in yourcluster-XYZseed namespace. It's possible that the addit…