Goal

Allow users to use NodeNetworkConfigurationPolicy to configure static cluster-unique IP addresses without hard-coding them.

User Stories

• As a cluster administrator,
  I want to configure static IPs on secondary NICs on a pool of nodes.
• I want to do so with a single policy,
  so I don't have to create one per each node,
  and so this policy is automatically applied on any newly added node.
• I want each of these static IPs to be unique,
  and taken from a defined range,
  and freed when needed.

Non-Requirements

• This epic does not cover IP address configuration of management NIC on day-0/1

Notes

• If at all possible, we should pick a solution that could be utilized even in the IPI nmstate API.
• Could we ease the requirement into the IP being taken from Node annotation. The annotation can be populated manually or by another controller. That would keep nmstate simple. It would be also useful for tasks other than IP management. And it would be a solid phase 1 implementation.
• This functionality was requested on U/S via https://github.com/nmstate/kubernetes-nmstate/issues/725
• This feature would prevent issues like: https://access.redhat.com/support/cases/#/case/03265987

Notes from demo

• Most of Whereabouts is not relevant for us, we should not depend on a big project for tiny part of its functionality
• We should be able to use pools in nmpolicy outside knmstate - the API should reflect it
• Pool should be only referenced from the policy, it should not be defined there
• Recording: https://drive.google.com/file/d/1ebg8dJ8J65t7E-dYg9YdkFrRN1qPKjac/view?usp=sharing

Done Checklist