Allow Upgrade or Swap VIP also when number of endpoints has been changed
Or allow the external IP address to be fixed/allocated to the Hosted Service.
The scenario is that during the lifetime of the application you may need to modify the number of endpoints, and re-deploy the solution BUT KEEP PUBLIC IP.
The best would be if Swap VIP could handle this - to avoid downtime, but I am willing to have some downtime as long as Upgrade is supported. This is to avoid service unavailable during the time DNS CNAME records are updated.
Thank you for suggesting this. This is in feature backlog and we’re looking at this again now for ARM IaaS VMs.
Nathan Lewis commented
As far as I can tell, endpoints cannot be edited on a cloud service.
The downtime comes from the required process to change the number of endpoints. You have to either delete staging and production and publish fresh, or setup a new cloud service and then change DNS / CNAME records from the old service to the new, etc.
Bart Verkoeijen commented
Narayan, yes, I've already been through that very unpleasant experience. Even though we have a staging environment, this issue requires downtime to be inflicted, and even worse, because of the DNS propagation this may linger much longer because the cached DNS records cause clients to go to the old (wrong) IP.
Thanks for your feedback. But are you saying that, updating endpoints (adding, deleting) on a cloud service causes downtime? And you lose the VIP as well in the process?