https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
a
What is the node ip(s)? (external/internal ip)
q
External: 49.12.xx.xx Internal: 10.0.0.5
a
So it doesn't account the internal ip
it's better not to use external ip then
q
Looks like it, but i didnt find any option to accept internal ips or add ip ranges
a
The issue might be with bootstraping cluster
before hcloud ccm
do you set node-ip explicitly
q
No, the nodes are created by the node driver
a
where from?
q
Hetzner, the ips are automaticly assigned. I don't choose any ip
a
the node driver?
q
And the internal ip is also auto assigned in the internal network
Oh
Any suggestions what i can do?
a
Well you could test more scenarios
q
For example?
a
if you don't specify external ip?
lets say don't assign public ip
q
I could disable public ip, but how would i then connect to the node to install the cloud-controller?
a
you don't need to install cloud controller on each node? only on control plane
with the control plane
q
so only disable for worker nodes?
a
let's say yes
q
i could try that
thanks
a
it's for a test
you can then file an issue with your findings
q
will do, thanks for the help 👍
Open in Slack
PreviousNext
Powered by