This message was deleted.
# general
a
This message was deleted.
m
Is it not possible to assign static IPs to these hosts? As far as I know, Kubernetes is very unhappy relying on DNS names and Rancher does not work at all as you've observed. Although, perhaps something has changed in that regard to help you.
c
Yes, you need to create DHCP reservations for your nodes, or give them static IPs.
🤕 1
d
I was hoping that wasn't the case as network team is very stingy on static IP and network reservations.
they don’t need to be static, just a DHCP reservation would work. As long as it gets the same IP when it restarts.
l
Just ask the netop guys, rather be stingy or have it work. It really is a simple question
d
I sent them the link and screen shots. Netops can be stingy
l
it has been a while since I worked in a larger group, but there has to be an awareness of basic needs to make it work. You can't run kubernetes with out ip's. It is a requirement not an optional need
d
They feel that the tools should be able to handle DHCP's IP address without reservations as many customers are deploying in the cloud and getting provided dynamic IP's via DHCP and have no way of getting static. that is there reasoning
l
Thats when you go to managment.
c
When you deploy to a cloud provider, you get a dynamic private IP - but that IP doesn’t change as long as the instance is provisioned. It is not at all unusual for things to want an IP that doesn’t change randomly when nodes are shut down or rebooted, if they’re not prepared to accommodate DHCP reservations then they’re just being stubborn for its own sake.
d
got my reservations.
so follow on questions @creamy-pencil-82913 , is there a way to use a DNS Pool? Question comes from when a reconfigure or expansion is needed it pulls a new DHCP address during reconfiguration which requires manual reservation setting.
c
That is below the level of anything Kubernetes is concerned about. That would be determined by how you are provisioning the underlying cluster nodes.