Network address migration between different networks by updating network configuration using a destination compute instance in a cloud environment to reduce disruptions

A non-transitory computer-readable medium having stored thereon instructions that, when executed by one or more processors, cause the one or more processors to:

• create a network interface using a private address within a subnet corresponding to the created network interface;
• register a first node of the HA pair with a service provider interface, the first node to be an active data server of the HA pair and a second node of the HA pair to be a backup node of the HA pair, wherein registering the first node of the HA pair with the service provider interface comprises at least adding an address of the first node to at least one route table corresponding to the service provider interface;
• service requests received by the first node of the HA pair by accessing the service provider interface using the at least one route table;
• detect a failure of the first node of the HA pair;
• register, with the second node of the HA pair and in response to the detection of the failure of the first node of the HA pair, the second node of the HA pair with the service provider interface by at least adding an address of the second node to the at least one route table corresponding to the service provider interface;
• and
• service requests received by the second node of the HA pair by accessing the service provider interface using the at least one route table.

A system comprising:

• a plurality of hardware processors configured to provide a cloud-based computing environment to provide network address migration utilizing a destination compute instance of a high availability (HA) pair to update a network configuration in a cloud computing environment, wherein the HA pair communicates with the cloud computing environment via, the hardware processors of the cloud-based computing environment configured to:
• create a network interface either using a private address within a subnet corresponding to the created network interface or using a floating address outside of the subnet corresponding to the created network interface;
• register a first node of the HA pair with a service provider interface, the first node to be an active data server of the HA pair and a second node of the HA pair to be a backup node of the HA pair, wherein registering the first node of the HA pair with the service provider interface comprises utilizing either the private address or the floating address, wherein registration comprises at least adding the floating address of the first node to at least one route table corresponding to the service provider interface if the created network interface utilizes the floating address;
• service requests received by the first node of the HA pair by accessing the service provider interface using the created network interface;
• detect a failure of the first node of the HA pair;
• determine, with the second node of the HA pair, whether the created network interface utilizes the private address or the floating address;
• perform a failover operation under control of the second node of the HA pair in response to detecting the failure of the first node of the HA pair, wherein if the first node of the HA pair was utilizing a floating address, the second node of the HA pair registers the second node of the HA pair with the service provider interface by at least adding an address of the second node to the at least one route table corresponding to the service provider interface;
• and
• service requests received by the second node of the HA pair after performing the failover operation under the control of the second node of the HA pair.