What happened:
The openshift-api api endpoints are created based on the existing IP address when microshift starts,
if the IP changes, the kubernetes controller can't connect to the endpoint, and starts failing.
What you expected to happen:
Microshift should have recognized the IP change and updated the endpoints, or used a VIP for the API purposes.
How to reproduce it (as minimally and precisely as possible):
- Assign an IP address to the MicroShift host
- Start MicroShift
- Change the IP address
- MicroShift stops working
- restart MicroShift
- MicroShift still not working
What happened:
The openshift-api api endpoints are created based on the existing IP address when microshift starts,
if the IP changes, the kubernetes controller can't connect to the endpoint, and starts failing.
What you expected to happen:
Microshift should have recognized the IP change and updated the endpoints, or used a VIP for the API purposes.
How to reproduce it (as minimally and precisely as possible):