As an OpenShift MetalLB administrator, I want the ability to assign a static IPv4 route to an interface without assigning an IPv4 address to it using nmstate, ensuring smooth routing functionalities like source-based and policy-based routing, especially in situations where MetalLB issues addresses. Given an OpenShift MetalLB administrator using nmstate for network configurations. When they attempt to implement source-based and policy-based routing configurations based on the given scenarios. Then nmstate should permit IPv4 static route assignments without IPv4 address bindings and ensure that all MetalLB-related routing configurations are successfully applied and operational. Definition of Done The implementation meets the acceptance criteria The unit tests and integration tests are written and passed The code is part of a build attached to an errata

Feature: The user is able to configure the static route when the address is empty. Reason: OpenShift MetalLB team requests to configure additional routes whenever the node does not have a configured IP address or route for the subnet in which MetalLB issues addresses. And in linux network stack, it does not matter what interface you add the address on a node (for example, loopback), the kernel is always processing arp-requests and sending arp-replies to any of them, this behavior is considered correct and, moreover, it is widely used in the a dynamic environment as Kubernetes. Result: The user is able to configure the static route when the address is empty.