kubermatic
Document static IP requirements for Nodes/Machines
We discussed and agreed on SIG Cluster Management that the ecosystem is pretty clearly expecting static IPs on Nodes, or to be more precise: Systems not changing their primary IP address once a cluster has been joined.
For now, we would like to document the requirement that VMs / hardware nodes get the same IP address assigned, even after reboots or DHCP leases expiring.
Also see https://github.com/kubermatic/kubermatic/issues/12218 for the investigation and code in the KubeVirt CCM that does not allow node changes.
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten