Hi - bit of a weird question admittedly…

I understand that in most instances, when a new deployment of something like an API server is pushed out there will be a period of time where both the old and new versions are running concurrently to avoid downtime. Is there a way to invert this - to ensure AT MOST 1 instance of a service is live at any time (and thus during rollovers it would temporarily drop down to 0)?