Stopping and Starting VMI SSH Connectivity Issues

[suneetnangia]

When VM is stopped using virtctl stop cmd, it deletes VMI resource from K8s and private IP assigned to the VMI resource is released to the pool. Later, when we start the VM using virtctl start cmd, no private IP is assigned to the actual Ubuntu VM even though it is configured for the newly created VMI resource.
It is due to this issue, SSH connectivity is lost, even though K8s service which is bound to external Azure LB is updated with the new private IP of VMI, for routing the traffic on port 22.