[Fixed] Moving klipper to the stub ccm broke our project #6452
mysticaltech
started this conversation in
General
Replies: 1 comment 4 replies
-
You know you can change the hetzner cloud-controller's listener port with the brandond@dev01:~$ docker run --rm -it hetznercloud/hcloud-cloud-controller-manager:v1.13.2 --help 2>&1 | grep secure-port
--bind-address ip The IP address on which to listen for the --secure-port port. The associated interface(s) must be reachable by the rest of the cluster, and by CLI/web clients. If blank or an unspecified address (0.0.0.0 or ::), all interfaces will be used. (default 0.0.0.0)
--secure-port int The port on which to serve HTTPS with authentication and authorization. If 0, don't serve HTTPS at all. (default 10258) I'll open an issue to make the k3s cloud-controller manager args configurable so that you can disable or reconfigure our port instead, if you prefer. In the mean time simply changing the hetzner port seems like a reasonable workaround. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello @brandond,
Just FYI, moving klipper to the ccm (as explained here) it broke one of our feature on kube-hetzner, because we are already using the hetzner ccm, and enabling klipper now breaks the cluster deployment, as port 10258 is already used by the stub ccm for klipper.
What a shame really! Now we have to changes lots of things in order to use metallb instead.
Beta Was this translation helpful? Give feedback.
All reactions