Explore the use of dummy interfaces to decouple etcd members from the node identity (IP). Under this spike explore:

• Assigning dummy interface "etcd0" to the node
• Assign /32 address to the newly created "etcd0"
• Define ip reachability to other control planes "etcd0" using static routes
• Explore if etcd can work under such setup
• Explore the type of work required to make such setup to work with any OCP deployment
• Explore "etcd0" for when node has multiple NICs to reach the other nodes (example, two paths for higher resiliency)
• Explore the use of this type of configuration to allow the use of dedicated links (NICs, clan interfaces, etc) for etcd synchronization. For example, if customer wants to have dedicate etcd sync link separated from the default OCP network
• Document findings & recommendations

Reference: Example of manually setting dummy interface in RHCOS images:

https://gist.github.com/williamcaban/6a2af58b1d99c21c172a697a94162bac