Skip to content

Conversation

@susverwimp
Copy link

What

Add static IP support for all nodes when Network is IPAM Managed

Why

Static IP is currently only supported for nodes with server role. This causes issues when docker decided to give different IPs to the nodes after a host reboot / daemon reload / ...

Implications

When the network is IPAM managed, both server and agent nodes will receive a static IP address instead of only the server roles.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR extends static IP assignment to all k3d nodes (both server and agent roles) when the network is IPAM managed, rather than only assigning static IPs to server nodes. This prevents issues that occur when Docker assigns different IPs to nodes after host reboots or daemon reloads.

  • The static IP assignment logic is moved outside the ServerRole-specific conditional block
  • Both server and agent nodes now receive static IPs when cluster.Network.IPAM.Managed is true

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant